MAYBE 964.92/297.84 MAYBE 964.92/297.84 964.92/297.84 We are left with following problem, upon which TcT provides the 964.92/297.84 certificate MAYBE. 964.92/297.84 964.92/297.84 Strict Trs: 964.92/297.84 { table() -> gen(s(0())) 964.92/297.84 , gen(x) -> if1(le(x, 10()), x) 964.92/297.84 , if1(false(), x) -> nil() 964.92/297.84 , if1(true(), x) -> if2(x, x) 964.92/297.84 , le(s(x), s(y)) -> le(x, y) 964.92/297.84 , le(s(x), 0()) -> false() 964.92/297.84 , le(0(), y) -> true() 964.92/297.84 , 10() -> s(s(s(s(s(s(s(s(s(s(0())))))))))) 964.92/297.84 , if2(x, y) -> if3(le(y, 10()), x, y) 964.92/297.84 , if3(false(), x, y) -> gen(s(x)) 964.92/297.84 , if3(true(), x, y) -> cons(entry(x, y, times(x, y)), if2(x, s(y))) 964.92/297.84 , times(s(x), y) -> plus(y, times(x, y)) 964.92/297.84 , times(0(), y) -> 0() 964.92/297.84 , plus(s(x), y) -> s(plus(x, y)) 964.92/297.84 , plus(0(), y) -> y } 964.92/297.84 Obligation: 964.92/297.84 innermost runtime complexity 964.92/297.84 Answer: 964.92/297.84 MAYBE 964.92/297.84 964.92/297.84 None of the processors succeeded. 964.92/297.84 964.92/297.84 Details of failed attempt(s): 964.92/297.84 ----------------------------- 964.92/297.84 1) 'empty' failed due to the following reason: 964.92/297.84 964.92/297.84 Empty strict component of the problem is NOT empty. 964.92/297.84 964.92/297.84 2) 'Best' failed due to the following reason: 964.92/297.84 964.92/297.84 None of the processors succeeded. 964.92/297.84 964.92/297.84 Details of failed attempt(s): 964.92/297.84 ----------------------------- 964.92/297.84 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 964.92/297.84 following reason: 964.92/297.84 964.92/297.84 Computation stopped due to timeout after 297.0 seconds. 964.92/297.84 964.92/297.84 2) 'Best' failed due to the following reason: 964.92/297.84 964.92/297.84 None of the processors succeeded. 964.92/297.84 964.92/297.84 Details of failed attempt(s): 964.92/297.84 ----------------------------- 964.92/297.84 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 964.92/297.84 seconds)' failed due to the following reason: 964.92/297.84 964.92/297.84 Computation stopped due to timeout after 148.0 seconds. 964.92/297.84 964.92/297.84 2) 'Best' failed due to the following reason: 964.92/297.84 964.92/297.84 None of the processors succeeded. 964.92/297.84 964.92/297.84 Details of failed attempt(s): 964.92/297.84 ----------------------------- 964.92/297.84 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 964.92/297.84 following reason: 964.92/297.84 964.92/297.84 The input cannot be shown compatible 964.92/297.84 964.92/297.84 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 964.92/297.84 to the following reason: 964.92/297.84 964.92/297.84 The input cannot be shown compatible 964.92/297.84 964.92/297.84 964.92/297.84 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 964.92/297.84 failed due to the following reason: 964.92/297.84 964.92/297.84 None of the processors succeeded. 964.92/297.84 964.92/297.84 Details of failed attempt(s): 964.92/297.84 ----------------------------- 964.92/297.84 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 964.92/297.84 failed due to the following reason: 964.92/297.84 964.92/297.84 match-boundness of the problem could not be verified. 964.92/297.84 964.92/297.84 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 964.92/297.84 failed due to the following reason: 964.92/297.84 964.92/297.84 match-boundness of the problem could not be verified. 964.92/297.84 964.92/297.84 964.92/297.84 964.92/297.84 964.92/297.84 964.92/297.84 Arrrr.. 965.24/298.07 EOF