This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Record likely upper bounds for loops


> Hi,
> 
> On Fri, 27 May 2016, Jan Hubicka wrote:
> > Thanks, updatted and comitted.
> 
> This checkin seems to regress gcc.c-torture/execute/20050826-2.c at -Os:
> 
> gcc/xgcc -Bgcc/ ../gcc/gcc/testsuite/gcc.c-torture/execute/20050826-2.c -Os \
>   -o ./20050826-2.exe  
> 
> ./20050826-2.exe
> Aborted
> 
> (the previous revision is fine)
Sorry,
I amanged to accidentally commit the following change:

Index: tree-ssa-loop-niter.c
===================================================================
--- tree-ssa-loop-niter.c	(revision 236816)
+++ tree-ssa-loop-niter.c	(working copy)
@@ -2289,11 +2289,7 @@ number_of_iterations_exit (struct loop *
 
   /* If NITER has simplified into a constant, update MAX.  */
   if (TREE_CODE (niter->niter) == INTEGER_CST)
-    {
-      niter->max = wi::to_widest (niter->niter);
-      record_niter_bound (loop, niter->max, loop_only_exit_p (loop, exit),
-			  true);
-    }
+    niter->max = wi::to_widest (niter->niter);
 
   if (integer_onep (niter->assumptions))
     return true;

I will revert it after re-testing.
Honza


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]