public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <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 12:01:00 -0000	[thread overview]
Message-ID: <bug-47344-4-Ai8Bxrc32n@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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steven at gcc dot gnu.org

--- Comment #9 from Steven Bosscher <steven at gcc dot gnu.org> 2013-03-06 12:01:27 UTC ---
(In reply to comment #8)
> All these regressions clutter the list of important regressions.

And why would all of these not be important?
Hiding a problem is not solving the problem.

And it always was policy that a regression should be marked as such. If
it is not important enough, you can set its priority to P4 or P5, but we
should never remove the regression marker.

See http://gcc.gnu.org/ml/gcc/2007-12/msg00550.html


  parent reply	other threads:[~2013-03-06 12:01 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
2013-03-06 12:01 ` steven at gcc dot gnu.org [this message]
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-Ai8Bxrc32n@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).