This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/68654] [6 Regression] CoreMark Pro performance degradation
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 08 Feb 2016 21:23:24 +0000
- Subject: [Bug tree-optimization/68654] [6 Regression] CoreMark Pro performance degradation
- Auto-submitted: auto-generated
- References: <bug-68654-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68654
--- Comment #23 from Jeffrey A. Law <law at redhat dot com> ---
I don't think it's worth the effort to try and keep that list sorted. I think
we can get what we want with a single walk over the IL just before coalescing.
That addresses the stability issue.
Then we will obviously want to look at whether or not there's something we're
missing in the coalescer. Maybe there's a reasonable tie-breaker that needs to
be added or some such. But until we have stability in the coalescing phase,
it's rather pointless to spend much effort on the coalescing algorithm as the
results may easily be skewed by the instabilities.