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