This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/69526] ivopts candidate strangeness
- From: "rdapp at linux dot vnet.ibm.com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 31 Mar 2016 11:56:30 +0000
- Subject: [Bug middle-end/69526] ivopts candidate strangeness
- Auto-submitted: auto-generated
- References: <bug-69526-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69526
--- Comment #10 from rdapp at linux dot vnet.ibm.com ---
Created attachment 38144
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38144&action=edit
Tentative patch for VRP and loop-doloop
Meanwhile I found the time to implement a pattern for VRP which seems to do the
job on tree level. Although larger now (and not many cases are covered yet) I
suppose I agree that it fits better in VRP than in ivopts and might even catch
more cases than before.
The fix on RTL level is nonetheless necessary since doloop calculates the
number of iterations independently of the code before and also adds a +1.
I cleaned up the fix a little by introducing niterp1_expr (niter plus 1) but
there's still room for improvement.
No regressions so far, improvement ideas welcome.