MAYBE 949.11/297.03 MAYBE 949.11/297.03 949.11/297.03 We are left with following problem, upon which TcT provides the 949.11/297.03 certificate MAYBE. 949.11/297.03 949.11/297.03 Strict Trs: 949.11/297.03 { eq(0(), 0()) -> true() 949.11/297.03 , eq(0(), s(m)) -> false() 949.11/297.03 , eq(s(n), 0()) -> false() 949.11/297.03 , eq(s(n), s(m)) -> eq(n, m) 949.11/297.03 , le(0(), m) -> true() 949.11/297.03 , le(s(n), 0()) -> false() 949.11/297.03 , le(s(n), s(m)) -> le(n, m) 949.11/297.03 , min(cons(n, cons(m, x))) -> if_min(le(n, m), cons(n, cons(m, x))) 949.11/297.03 , min(cons(x, nil())) -> x 949.11/297.03 , if_min(true(), cons(n, cons(m, x))) -> min(cons(n, x)) 949.11/297.03 , if_min(false(), cons(n, cons(m, x))) -> min(cons(m, x)) 949.11/297.03 , replace(n, m, cons(k, x)) -> 949.11/297.03 if_replace(eq(n, k), n, m, cons(k, x)) 949.11/297.03 , replace(n, m, nil()) -> nil() 949.11/297.03 , if_replace(true(), n, m, cons(k, x)) -> cons(m, x) 949.11/297.03 , if_replace(false(), n, m, cons(k, x)) -> 949.11/297.03 cons(k, replace(n, m, x)) 949.11/297.03 , empty(cons(n, x)) -> false() 949.11/297.03 , empty(nil()) -> true() 949.11/297.03 , head(cons(n, x)) -> n 949.11/297.03 , tail(cons(n, x)) -> x 949.11/297.03 , tail(nil()) -> nil() 949.11/297.03 , sort(x) -> sortIter(x, nil()) 949.11/297.03 , sortIter(x, y) -> 949.11/297.03 if(empty(x), x, y, append(y, cons(min(x), nil()))) 949.11/297.03 , if(true(), x, y, z) -> y 949.11/297.03 , if(false(), x, y, z) -> 949.11/297.03 sortIter(replace(min(x), head(x), tail(x)), z) } 949.11/297.03 Obligation: 949.11/297.03 innermost runtime complexity 949.11/297.03 Answer: 949.11/297.03 MAYBE 949.11/297.03 949.11/297.03 None of the processors succeeded. 949.11/297.03 949.11/297.03 Details of failed attempt(s): 949.11/297.03 ----------------------------- 949.11/297.03 1) 'empty' failed due to the following reason: 949.11/297.03 949.11/297.03 Empty strict component of the problem is NOT empty. 949.11/297.03 949.11/297.03 2) 'Best' failed due to the following reason: 949.11/297.03 949.11/297.03 None of the processors succeeded. 949.11/297.03 949.11/297.03 Details of failed attempt(s): 949.11/297.03 ----------------------------- 949.11/297.03 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 949.11/297.03 following reason: 949.11/297.03 949.11/297.03 Computation stopped due to timeout after 297.0 seconds. 949.11/297.03 949.11/297.03 2) 'Best' failed due to the following reason: 949.11/297.03 949.11/297.03 None of the processors succeeded. 949.11/297.03 949.11/297.03 Details of failed attempt(s): 949.11/297.03 ----------------------------- 949.11/297.03 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 949.11/297.03 seconds)' failed due to the following reason: 949.11/297.03 949.11/297.03 Computation stopped due to timeout after 148.0 seconds. 949.11/297.03 949.11/297.03 2) 'Best' failed due to the following reason: 949.11/297.03 949.11/297.03 None of the processors succeeded. 949.11/297.03 949.11/297.03 Details of failed attempt(s): 949.11/297.03 ----------------------------- 949.11/297.03 1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 949.11/297.03 to the following reason: 949.11/297.03 949.11/297.03 The input cannot be shown compatible 949.11/297.03 949.11/297.03 2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 949.11/297.03 following reason: 949.11/297.03 949.11/297.03 The input cannot be shown compatible 949.11/297.03 949.11/297.03 949.11/297.03 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 949.11/297.03 failed due to the following reason: 949.11/297.03 949.11/297.03 None of the processors succeeded. 949.11/297.03 949.11/297.03 Details of failed attempt(s): 949.11/297.03 ----------------------------- 949.11/297.03 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 949.11/297.03 failed due to the following reason: 949.11/297.03 949.11/297.03 match-boundness of the problem could not be verified. 949.11/297.03 949.11/297.03 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 949.11/297.03 failed due to the following reason: 949.11/297.03 949.11/297.03 match-boundness of the problem could not be verified. 949.11/297.03 949.11/297.03 949.11/297.03 949.11/297.03 949.11/297.03 949.11/297.03 Arrrr.. 949.21/297.25 EOF