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] |
That is not true. I worked on many compiler time regression bugs. I remeber one serious degradation of compilation time on all_cp2k_gfortran.f90. I solved the problem and make IRA working faster and generating much better code than the old RA.From: Ian Lance Taylor <iant@google.com> Date: Mon, 1 Oct 2012 11:55:56 -0700
Steven is correct in saying that there is a tendency to move on and never address GCC bugs. However, there is also a counter-vailing tendency to fix GCC bugs. Anyhow I'm certainly not saying that in all cases it's OK to accept a merge with regressions; I'm saying that in this specific case it is OK.I think it's more important in this case to recognize Steven's real point, which is that for an identical situation (IRA), and with an identical patch author, we had similar bugs. They were promised to be worked on, and yet some of those regressions are still very much with us.
The likelyhood of a repeat is therefore very real.Wrong assumptions result in wrong conclusions.
I really don't have a lot of confidence given what has happened in the past. I also don't understand what's so evil about sorting this out on a branch. It's the perfect carrot to get the compile time regressions fixed.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |