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