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