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