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 tree-optimization/40436] [4.5 regression] 0.5% code size regression caused by r147852
Date: Tue, 06 Apr 2010 11:00:00 -0000 [thread overview]
Message-ID: <20100406110008.14657.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40436-374@http.gcc.gnu.org/bugzilla/>
------- Comment #31 from rguenther at suse dot de 2010-04-06 11:00 -------
Subject: Re: [4.5 regression] 0.5% code size
regression caused by r147852
On Tue, 6 Apr 2010, steven at gcc dot gnu dot org wrote:
> ------- Comment #30 from steven at gcc dot gnu dot org 2010-04-06 10:56 -------
> I think it is a really, really bad signal if a bug like this, where the
> revision that introduced the issue was identified >9 months ago, remains
> unfixed for GCC 4.5.
>
> I, for one, wouldn't care hunting down revisions that introduce regressions in
> stage1 anymore, if component maintainers and release managers just postpone
> fixing the issue until it is too late to fix for a release.
Well, the fix doesn't fix this bug. There's no patch to fix this
bug (yet). Also 0.5% code size increase doesn't look important
enough to me.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40436
next prev parent reply other threads:[~2010-04-06 11:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 22:35 [Bug tree-optimization/40436] New: " rearnsha at gcc dot gnu dot org
2009-06-13 22:51 ` [Bug tree-optimization/40436] " rguenth at gcc dot gnu dot org
2009-06-13 22:53 ` rguenth at gcc dot gnu dot org
2009-06-13 23:07 ` pinskia at gcc dot gnu dot org
2009-06-13 23:10 ` rearnsha at gcc dot gnu dot org
2009-06-13 23:27 ` rearnsha at gcc dot gnu dot org
2009-06-14 13:31 ` rguenth at gcc dot gnu dot org
2009-06-19 0:00 ` ramana at gcc dot gnu dot org
2009-06-19 23:14 ` ramana at gcc dot gnu dot org
2009-06-30 12:44 ` hubicka at gcc dot gnu dot org
2009-06-30 12:46 ` hubicka at ucw dot cz
2009-06-30 13:14 ` steven at gcc dot gnu dot org
2009-06-30 13:41 ` hubicka at gcc dot gnu dot org
2009-06-30 19:56 ` steven at gcc dot gnu dot org
2009-06-30 23:37 ` hubicka at ucw dot cz
2009-07-01 5:41 ` steven at gcc dot gnu dot org
2009-07-02 10:11 ` hubicka at ucw dot cz
2009-07-09 15:39 ` rguenth at gcc dot gnu dot org
2009-12-09 17:09 ` ramana at gcc dot gnu dot org
2010-03-07 20:37 ` hubicka at gcc dot gnu dot org
2010-03-28 15:47 ` rguenth at gcc dot gnu dot org
2010-03-28 16:34 ` hubicka at ucw dot cz
2010-03-28 16:43 ` rguenther at suse dot de
2010-03-28 16:56 ` hubicka at ucw dot cz
2010-03-28 17:00 ` rguenther at suse dot de
2010-03-28 17:30 ` hubicka at ucw dot cz
2010-04-03 21:02 ` hubicka at ucw dot cz
2010-04-03 21:13 ` rguenther at suse dot de
2010-04-03 21:19 ` hubicka at ucw dot cz
2010-04-03 21:21 ` hubicka at ucw dot cz
2010-04-03 21:39 ` hubicka at ucw dot cz
2010-04-06 10:36 ` matz at gcc dot gnu dot org
2010-04-06 10:46 ` hubicka at ucw dot cz
2010-04-06 10:57 ` steven at gcc dot gnu dot org
2010-04-06 11:00 ` rguenther at suse dot de [this message]
2010-04-06 11:05 ` hubicka at ucw dot cz
2010-04-06 11:10 ` matz at gcc dot gnu dot org
2010-04-06 11:37 ` steven at gcc dot gnu dot org
2010-04-06 11:39 ` rguenth at gcc dot gnu dot org
2010-07-31 9:35 ` [Bug tree-optimization/40436] [4.5/4.6 " rguenth at gcc dot gnu dot 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=20100406110008.14657.qmail@sourceware.org \
--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).