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