This is the mail archive of the gcc-bugs@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]

[Bug middle-end/47344] [4.6/4.7/4.8 Regression][meta-bug] GCC gets slower and uses more memory


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47344

--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> 2013-03-06 10:57:15 UTC ---
On Wed, 6 Mar 2013, steven at gcc dot gnu.org wrote:

> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47344
> 
> --- Comment #7 from Steven Bosscher <steven at gcc dot gnu.org> 2013-03-06 10:51:27 UTC ---
> This bug looks like the wrong idea to me. Old is apparently anything
> older than the maintained release branches, but many users "in the field"
> still use older compilers that come with their respective distributions.
> 
> For instance a regresion that is present since GCC 4.6 but not in GCC 4.5
> gets reduced in importance and visibility by not marking it as regression
> and instead only adding it to this grab-a-bag PR. Example of such a case
> is bug 53958.
> 
> This is a change of old existing policy that any regression should be
> marked as such. This policy change should have been discussed (and IMHO
> rejected) on the GCC mailing list.
> 
> Also, this meta-bug depends on not-so-old regressions, so it's already
> more like a collection of compile/memory hog issues than a collection
> point for apparently "unimportant" regressions.

All these regressions clutter the list of important regressions.
All of them are present in more or less severe form in all maintained
branches.

There is a similar issue for missed-optimization regressions that
are long-standing.


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