MAYBE 787.53/297.10 MAYBE 787.53/297.10 787.53/297.10 We are left with following problem, upon which TcT provides the 787.53/297.10 certificate MAYBE. 787.53/297.10 787.53/297.10 Strict Trs: 787.53/297.10 { active(and(X1, X2)) -> and(active(X1), X2) 787.53/297.10 , active(and(tt(), X)) -> mark(X) 787.53/297.10 , active(plus(X1, X2)) -> plus(X1, active(X2)) 787.53/297.10 , active(plus(X1, X2)) -> plus(active(X1), X2) 787.53/297.10 , active(plus(N, 0())) -> mark(N) 787.53/297.10 , active(plus(N, s(M))) -> mark(s(plus(N, M))) 787.53/297.10 , active(s(X)) -> s(active(X)) 787.53/297.10 , active(x(X1, X2)) -> x(X1, active(X2)) 787.53/297.10 , active(x(X1, X2)) -> x(active(X1), X2) 787.53/297.10 , active(x(N, 0())) -> mark(0()) 787.53/297.10 , active(x(N, s(M))) -> mark(plus(x(N, M), N)) 787.53/297.10 , and(mark(X1), X2) -> mark(and(X1, X2)) 787.53/297.10 , and(ok(X1), ok(X2)) -> ok(and(X1, X2)) 787.53/297.10 , plus(X1, mark(X2)) -> mark(plus(X1, X2)) 787.53/297.10 , plus(mark(X1), X2) -> mark(plus(X1, X2)) 787.53/297.10 , plus(ok(X1), ok(X2)) -> ok(plus(X1, X2)) 787.53/297.10 , s(mark(X)) -> mark(s(X)) 787.53/297.10 , s(ok(X)) -> ok(s(X)) 787.53/297.10 , x(X1, mark(X2)) -> mark(x(X1, X2)) 787.53/297.10 , x(mark(X1), X2) -> mark(x(X1, X2)) 787.53/297.10 , x(ok(X1), ok(X2)) -> ok(x(X1, X2)) 787.53/297.10 , proper(and(X1, X2)) -> and(proper(X1), proper(X2)) 787.53/297.10 , proper(tt()) -> ok(tt()) 787.53/297.10 , proper(plus(X1, X2)) -> plus(proper(X1), proper(X2)) 787.53/297.10 , proper(0()) -> ok(0()) 787.53/297.10 , proper(s(X)) -> s(proper(X)) 787.53/297.10 , proper(x(X1, X2)) -> x(proper(X1), proper(X2)) 787.53/297.10 , top(mark(X)) -> top(proper(X)) 787.53/297.10 , top(ok(X)) -> top(active(X)) } 787.53/297.10 Obligation: 787.53/297.10 innermost runtime complexity 787.53/297.10 Answer: 787.53/297.10 MAYBE 787.53/297.10 787.53/297.10 None of the processors succeeded. 787.53/297.10 787.53/297.10 Details of failed attempt(s): 787.53/297.10 ----------------------------- 787.53/297.10 1) 'empty' failed due to the following reason: 787.53/297.10 787.53/297.10 Empty strict component of the problem is NOT empty. 787.53/297.10 787.53/297.10 2) 'Best' failed due to the following reason: 787.53/297.10 787.53/297.10 None of the processors succeeded. 787.53/297.10 787.53/297.10 Details of failed attempt(s): 787.53/297.10 ----------------------------- 787.53/297.10 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 787.53/297.10 following reason: 787.53/297.10 787.53/297.10 Computation stopped due to timeout after 297.0 seconds. 787.53/297.10 787.53/297.10 2) 'Best' failed due to the following reason: 787.53/297.10 787.53/297.10 None of the processors succeeded. 787.53/297.10 787.53/297.10 Details of failed attempt(s): 787.53/297.10 ----------------------------- 787.53/297.10 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 787.53/297.10 seconds)' failed due to the following reason: 787.53/297.10 787.53/297.10 Computation stopped due to timeout after 148.0 seconds. 787.53/297.10 787.53/297.10 2) 'Best' failed due to the following reason: 787.53/297.10 787.53/297.10 None of the processors succeeded. 787.53/297.10 787.53/297.10 Details of failed attempt(s): 787.53/297.10 ----------------------------- 787.53/297.10 1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 787.53/297.10 to the following reason: 787.53/297.10 787.53/297.10 The input cannot be shown compatible 787.53/297.10 787.53/297.10 2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 787.53/297.10 following reason: 787.53/297.10 787.53/297.10 The input cannot be shown compatible 787.53/297.10 787.53/297.10 787.53/297.10 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 787.53/297.10 failed due to the following reason: 787.53/297.10 787.53/297.10 None of the processors succeeded. 787.53/297.10 787.53/297.10 Details of failed attempt(s): 787.53/297.10 ----------------------------- 787.53/297.10 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 787.53/297.10 failed due to the following reason: 787.53/297.10 787.53/297.10 match-boundness of the problem could not be verified. 787.53/297.10 787.53/297.10 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 787.53/297.10 failed due to the following reason: 787.53/297.10 787.53/297.10 match-boundness of the problem could not be verified. 787.53/297.10 787.53/297.10 787.53/297.10 787.53/297.10 787.53/297.10 787.53/297.10 Arrrr.. 787.53/297.16 EOF