MAYBE 887.13/297.02 MAYBE 887.13/297.02 887.13/297.02 We are left with following problem, upon which TcT provides the 887.13/297.02 certificate MAYBE. 887.13/297.02 887.13/297.02 Strict Trs: 887.13/297.02 { length(nil()) -> 0() 887.13/297.02 , length(cons(x, l)) -> s(length(l)) 887.13/297.02 , lt(x, 0()) -> false() 887.13/297.02 , lt(0(), s(y)) -> true() 887.13/297.02 , lt(s(x), s(y)) -> lt(x, y) 887.13/297.02 , head(nil()) -> undefined() 887.13/297.02 , head(cons(x, l)) -> x 887.13/297.02 , tail(nil()) -> nil() 887.13/297.02 , tail(cons(x, l)) -> l 887.13/297.02 , reverse(l) -> rev(0(), l, nil(), l) 887.13/297.02 , rev(x, l, accu, orig) -> 887.13/297.02 if(lt(x, length(orig)), x, l, accu, orig) 887.13/297.02 , if(false(), x, l, accu, orig) -> accu 887.13/297.02 , if(true(), x, l, accu, orig) -> 887.13/297.02 rev(s(x), tail(l), cons(head(l), accu), orig) } 887.13/297.02 Obligation: 887.13/297.02 innermost runtime complexity 887.13/297.02 Answer: 887.13/297.02 MAYBE 887.13/297.02 887.13/297.02 None of the processors succeeded. 887.13/297.02 887.13/297.02 Details of failed attempt(s): 887.13/297.02 ----------------------------- 887.13/297.02 1) 'empty' failed due to the following reason: 887.13/297.02 887.13/297.02 Empty strict component of the problem is NOT empty. 887.13/297.02 887.13/297.02 2) 'Best' failed due to the following reason: 887.13/297.02 887.13/297.02 None of the processors succeeded. 887.13/297.02 887.13/297.02 Details of failed attempt(s): 887.13/297.02 ----------------------------- 887.13/297.02 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 887.13/297.02 following reason: 887.13/297.02 887.13/297.02 Computation stopped due to timeout after 297.0 seconds. 887.13/297.02 887.13/297.02 2) 'Best' failed due to the following reason: 887.13/297.02 887.13/297.02 None of the processors succeeded. 887.13/297.02 887.13/297.02 Details of failed attempt(s): 887.13/297.02 ----------------------------- 887.13/297.02 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 887.13/297.02 seconds)' failed due to the following reason: 887.13/297.02 887.13/297.02 Computation stopped due to timeout after 148.0 seconds. 887.13/297.02 887.13/297.02 2) 'Best' failed due to the following reason: 887.13/297.02 887.13/297.02 None of the processors succeeded. 887.13/297.02 887.13/297.02 Details of failed attempt(s): 887.13/297.02 ----------------------------- 887.13/297.02 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 887.13/297.02 following reason: 887.13/297.02 887.13/297.02 The input cannot be shown compatible 887.13/297.02 887.13/297.02 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 887.13/297.02 to the following reason: 887.13/297.02 887.13/297.02 The input cannot be shown compatible 887.13/297.02 887.13/297.02 887.13/297.02 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 887.13/297.02 failed due to the following reason: 887.13/297.02 887.13/297.02 None of the processors succeeded. 887.13/297.02 887.13/297.02 Details of failed attempt(s): 887.13/297.02 ----------------------------- 887.13/297.02 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 887.13/297.02 failed due to the following reason: 887.13/297.02 887.13/297.02 match-boundness of the problem could not be verified. 887.13/297.02 887.13/297.02 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 887.13/297.02 failed due to the following reason: 887.13/297.02 887.13/297.02 match-boundness of the problem could not be verified. 887.13/297.02 887.13/297.02 887.13/297.02 887.13/297.02 887.13/297.02 887.13/297.02 Arrrr.. 887.35/297.22 EOF