public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47344] [4.6/4.7/4.8 Regression][meta-bug] GCC gets slower and uses more memory
Date: Wed, 06 Mar 2013 10:57:00 -0000	[thread overview]
Message-ID: <bug-47344-4-lR26a1FsSL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47344-4@http.gcc.gnu.org/bugzilla/>


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.


  parent reply	other threads:[~2013-03-06 10:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 14:23 [Bug middle-end/47344] New: [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu.org
2011-01-18 14:24 ` [Bug middle-end/47344] " rguenth at gcc dot gnu.org
2011-01-19 22:00 ` jakub at gcc dot gnu.org
2011-06-27 14:50 ` [Bug middle-end/47344] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2011-11-07  9:13 ` [Bug middle-end/47344] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-02-22 13:47 ` xiaoyuanbo at yeah dot net
2012-03-13 15:03 ` [Bug middle-end/47344] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 11:31 ` rguenth at gcc dot gnu.org
2013-03-06 10:52 ` [Bug middle-end/47344] [4.6/4.7/4.8 " steven at gcc dot gnu.org
2013-03-06 10:57 ` rguenther at suse dot de [this message]
2013-03-06 12:01 ` steven at gcc dot gnu.org
2013-03-06 12:08 ` jakub at gcc dot gnu.org
2013-03-06 12:12 ` rguenth at gcc dot gnu.org
2013-04-12 15:17 ` [Bug middle-end/47344] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2014-06-12 13:25 ` [Bug middle-end/47344] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-06-12 13:49 ` rguenth at gcc dot gnu.org
2014-12-19 13:33 ` [Bug middle-end/47344] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23  8:26 ` [Bug middle-end/47344] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:00 ` [Bug middle-end/47344] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:31 ` jakub at gcc dot gnu.org
2021-05-14  9:46 ` [Bug middle-end/47344] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:05 ` rguenth at gcc dot gnu.org
2022-05-27  9:34 ` [Bug middle-end/47344] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:29 ` jakub at gcc dot gnu.org
2023-07-07 10:29 ` [Bug middle-end/47344] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-02-20 12:30 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-47344-4-lR26a1FsSL@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).