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