MAYBE 718.04/297.09 MAYBE 718.04/297.09 718.04/297.09 We are left with following problem, upon which TcT provides the 718.04/297.09 certificate MAYBE. 718.04/297.09 718.04/297.09 Strict Trs: 718.04/297.09 { cond1(true(), x) -> cond2(even(x), x) 718.04/297.09 , cond2(true(), x) -> cond1(neq(x, 0()), div2(x)) 718.04/297.09 , cond2(false(), x) -> cond1(neq(x, 0()), p(x)) 718.04/297.09 , even(0()) -> true() 718.04/297.09 , even(s(0())) -> false() 718.04/297.09 , even(s(s(x))) -> even(x) 718.04/297.09 , neq(0(), 0()) -> false() 718.04/297.09 , neq(0(), s(x)) -> true() 718.04/297.09 , neq(s(x), 0()) -> true() 718.04/297.09 , neq(s(x), s(y())) -> neq(x, y()) 718.04/297.09 , div2(0()) -> 0() 718.04/297.09 , div2(s(0())) -> 0() 718.04/297.09 , div2(s(s(x))) -> s(div2(x)) 718.04/297.09 , p(0()) -> 0() 718.04/297.09 , p(s(x)) -> x } 718.04/297.09 Obligation: 718.04/297.09 innermost runtime complexity 718.04/297.09 Answer: 718.04/297.09 MAYBE 718.04/297.09 718.04/297.09 None of the processors succeeded. 718.04/297.09 718.04/297.09 Details of failed attempt(s): 718.04/297.09 ----------------------------- 718.04/297.09 1) 'empty' failed due to the following reason: 718.04/297.09 718.04/297.09 Empty strict component of the problem is NOT empty. 718.04/297.09 718.04/297.09 2) 'Best' failed due to the following reason: 718.04/297.09 718.04/297.09 None of the processors succeeded. 718.04/297.09 718.04/297.09 Details of failed attempt(s): 718.04/297.09 ----------------------------- 718.04/297.09 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 718.04/297.09 following reason: 718.04/297.09 718.04/297.09 Computation stopped due to timeout after 297.0 seconds. 718.04/297.09 718.04/297.09 2) 'Best' failed due to the following reason: 718.04/297.09 718.04/297.09 None of the processors succeeded. 718.04/297.09 718.04/297.09 Details of failed attempt(s): 718.04/297.09 ----------------------------- 718.04/297.09 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 718.04/297.09 seconds)' failed due to the following reason: 718.04/297.09 718.04/297.09 Computation stopped due to timeout after 148.0 seconds. 718.04/297.09 718.04/297.09 2) 'Best' failed due to the following reason: 718.04/297.09 718.04/297.09 None of the processors succeeded. 718.04/297.09 718.04/297.09 Details of failed attempt(s): 718.04/297.09 ----------------------------- 718.04/297.09 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 718.04/297.09 following reason: 718.04/297.09 718.04/297.09 The input cannot be shown compatible 718.04/297.09 718.04/297.09 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 718.04/297.09 to the following reason: 718.04/297.09 718.04/297.09 The input cannot be shown compatible 718.04/297.09 718.04/297.09 718.04/297.09 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 718.04/297.09 failed due to the following reason: 718.04/297.09 718.04/297.09 None of the processors succeeded. 718.04/297.09 718.04/297.09 Details of failed attempt(s): 718.04/297.09 ----------------------------- 718.04/297.09 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 718.04/297.09 failed due to the following reason: 718.04/297.09 718.04/297.09 match-boundness of the problem could not be verified. 718.04/297.09 718.04/297.09 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 718.04/297.09 failed due to the following reason: 718.04/297.09 718.04/297.09 match-boundness of the problem could not be verified. 718.04/297.09 718.04/297.09 718.04/297.09 718.04/297.09 718.04/297.09 718.04/297.09 Arrrr.. 718.14/297.13 EOF