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