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