MAYBE
914.04/297.02	MAYBE
914.04/297.02	
914.04/297.02	We are left with following problem, upon which TcT provides the
914.04/297.02	certificate MAYBE.
914.04/297.02	
914.04/297.02	Strict Trs:
914.04/297.02	  { plus(x, y) -> plusIter(x, y, 0())
914.04/297.02	  , plusIter(x, y, z) -> ifPlus(le(x, z), x, y, z)
914.04/297.02	  , ifPlus(true(), x, y, z) -> y
914.04/297.02	  , ifPlus(false(), x, y, z) -> plusIter(x, s(y), s(z))
914.04/297.02	  , le(0(), y) -> true()
914.04/297.02	  , le(s(x), 0()) -> false()
914.04/297.02	  , le(s(x), s(y)) -> le(x, y)
914.04/297.02	  , sum(xs) -> sumIter(xs, 0())
914.04/297.02	  , sumIter(xs, x) -> ifSum(isempty(xs), xs, x, plus(x, head(xs)))
914.04/297.02	  , ifSum(true(), xs, x, y) -> x
914.04/297.02	  , ifSum(false(), xs, x, y) -> sumIter(tail(xs), y)
914.04/297.02	  , isempty(nil()) -> true()
914.04/297.02	  , isempty(cons(x, xs)) -> false()
914.04/297.02	  , head(nil()) -> error()
914.04/297.02	  , head(cons(x, xs)) -> x
914.04/297.02	  , tail(nil()) -> nil()
914.04/297.02	  , tail(cons(x, xs)) -> xs
914.04/297.02	  , a() -> b()
914.04/297.02	  , a() -> c() }
914.04/297.02	Obligation:
914.04/297.02	  innermost runtime complexity
914.04/297.02	Answer:
914.04/297.02	  MAYBE
914.04/297.02	
914.04/297.02	None of the processors succeeded.
914.04/297.02	
914.04/297.02	Details of failed attempt(s):
914.04/297.02	-----------------------------
914.04/297.02	1) 'empty' failed due to the following reason:
914.04/297.02	   
914.04/297.02	   Empty strict component of the problem is NOT empty.
914.04/297.02	
914.04/297.02	2) 'Best' failed due to the following reason:
914.04/297.02	   
914.04/297.02	   None of the processors succeeded.
914.04/297.02	   
914.04/297.02	   Details of failed attempt(s):
914.04/297.02	   -----------------------------
914.04/297.02	   1) 'With Problem ... (timeout of 297 seconds)' failed due to the
914.04/297.02	      following reason:
914.04/297.02	      
914.04/297.02	      Computation stopped due to timeout after 297.0 seconds.
914.04/297.02	   
914.04/297.02	   2) 'Best' failed due to the following reason:
914.04/297.02	      
914.04/297.02	      None of the processors succeeded.
914.04/297.02	      
914.04/297.02	      Details of failed attempt(s):
914.04/297.02	      -----------------------------
914.04/297.02	      1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
914.04/297.02	         seconds)' failed due to the following reason:
914.04/297.02	         
914.04/297.02	         Computation stopped due to timeout after 148.0 seconds.
914.04/297.02	      
914.04/297.02	      2) 'Best' failed due to the following reason:
914.04/297.02	         
914.04/297.02	         None of the processors succeeded.
914.04/297.02	         
914.04/297.02	         Details of failed attempt(s):
914.04/297.02	         -----------------------------
914.04/297.02	         1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
914.04/297.02	            to the following reason:
914.04/297.02	            
914.04/297.02	            The input cannot be shown compatible
914.04/297.02	         
914.04/297.02	         2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
914.04/297.02	            following reason:
914.04/297.02	            
914.04/297.02	            The input cannot be shown compatible
914.04/297.02	         
914.04/297.02	      
914.04/297.02	      3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
914.04/297.02	         failed due to the following reason:
914.04/297.02	         
914.04/297.02	         None of the processors succeeded.
914.04/297.02	         
914.04/297.02	         Details of failed attempt(s):
914.04/297.02	         -----------------------------
914.04/297.02	         1) 'Bounds with minimal-enrichment and initial automaton 'match''
914.04/297.02	            failed due to the following reason:
914.04/297.02	            
914.04/297.02	            match-boundness of the problem could not be verified.
914.04/297.02	         
914.04/297.02	         2) 'Bounds with perSymbol-enrichment and initial automaton 'match''
914.04/297.02	            failed due to the following reason:
914.04/297.02	            
914.04/297.02	            match-boundness of the problem could not be verified.
914.04/297.02	         
914.04/297.02	      
914.04/297.02	   
914.04/297.02	
914.04/297.02	
914.04/297.02	Arrrr..
914.37/297.32	EOF