This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/69042] [6 regression] Missed optimization in ivopts
- From: "amker at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 09 Mar 2016 09:59:57 +0000
- Subject: [Bug tree-optimization/69042] [6 regression] Missed optimization in ivopts
- Auto-submitted: auto-generated
- References: <bug-69042-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69042
--- Comment #9 from amker at gcc dot gnu.org ---
(In reply to amker from comment #8)
> Though adding candidate with offset stripped from base helps this case, it
> causes other regressions which I need to understand.
I can confirm that one major regression on AArch64 for spec2k is in 173.applu.
The root cause is this change increases candidate number. The number exceeds
the default "--param iv-consider-all-candidates-bound=30". It can be resolved
by increasing this param.
Other regressions seem false alarms, I couldn't reproduce it.
There are some small improvements in other cases, overall the spec2k perf isn't
changed on AArch64. I will check spec2k6 and will send the patch if there is
no regression either.
And can we increase the param bound a little now (or in GCC 7)?