public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/47166] [4.5 Regression] SpecCpu2000 Ammp segfaults for ARM with -O3 -mthumb
Date: Tue, 01 Feb 2011 01:16:00 -0000 [thread overview]
Message-ID: <bug-47166-4-B8AjJ2LsXK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47166-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47166
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramana at gcc dot gnu.org
--- Comment #25 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2011-02-01 01:16:08 UTC ---
(In reply to comment #15)
> > I don't see how this makes any sense. We've identified two bugs in reload, both
> > leading to incorrect code, and you'd rather revert the fix for one than fix
> > both?
>
> Yes, because the first one wasn't a regression and fixing the second may well
> cause a third to pop up, you never know with reload. This is called RM...
I am curious to know what we are doing with this ?.
The patch for PR41085 caused this regression for ARM with the 4.5 branch and
this fix is to fix the issue exposed by the fix for PR41085. Are we going to
revert the fix for PR41085 or are we going to backport the current fix for this
?
Thanks
Ramana
next prev parent reply other threads:[~2011-02-01 1:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 11:53 [Bug rtl-optimization/47166] New: [4.5 4.6 " ibolton at gcc dot gnu.org
2011-01-04 12:03 ` [Bug rtl-optimization/47166] " bernds at gcc dot gnu.org
2011-01-04 12:30 ` ibolton at gcc dot gnu.org
2011-01-04 12:32 ` ibolton at gcc dot gnu.org
2011-01-05 6:10 ` hp at gcc dot gnu.org
2011-01-05 8:21 ` hp at gcc dot gnu.org
2011-01-05 14:42 ` ibolton at gcc dot gnu.org
2011-01-05 16:50 ` ibolton at gcc dot gnu.org
2011-01-11 12:35 ` [Bug rtl-optimization/47166] [4.5/4.6 " rguenth at gcc dot gnu.org
2011-01-11 16:16 ` bernds at gcc dot gnu.org
2011-01-11 17:30 ` bernds at gcc dot gnu.org
2011-01-11 18:06 ` ibolton at gcc dot gnu.org
2011-01-12 10:43 ` ibolton at gcc dot gnu.org
2011-01-12 10:49 ` ibolton at gcc dot gnu.org
2011-01-15 16:15 ` [Bug rtl-optimization/47166] [4.5.2/4.6 " ebotcazou at gcc dot gnu.org
2011-01-19 20:01 ` bernds at gcc dot gnu.org
2011-01-19 20:16 ` ebotcazou at gcc dot gnu.org
2011-01-19 20:49 ` hp at gcc dot gnu.org
2011-01-19 23:14 ` ebotcazou at gcc dot gnu.org
2011-01-20 11:06 ` [Bug rtl-optimization/47166] [4.5/4.6 " rguenth at gcc dot gnu.org
2011-01-20 18:06 ` hp at gcc dot gnu.org
2011-01-23 22:41 ` bernds at gcc dot gnu.org
2011-01-24 14:47 ` jakub at gcc dot gnu.org
2011-01-24 15:30 ` ibolton at gcc dot gnu.org
2011-01-25 14:11 ` ibolton at gcc dot gnu.org
2011-01-25 16:19 ` [Bug rtl-optimization/47166] [4.5 " jakub at gcc dot gnu.org
2011-02-01 1:16 ` ramana at gcc dot gnu.org [this message]
2011-02-01 1:35 ` bernds at gcc dot gnu.org
2011-02-01 1:39 ` ramana.r at gmail dot com
2011-02-11 16:05 ` bernds at gcc dot gnu.org
2011-02-11 16:15 ` bernds at gcc dot gnu.org
2011-02-15 15:48 ` ibolton at gcc dot gnu.org
2011-03-14 13:46 ` rsandifo at gcc dot gnu.org
2011-03-14 13:49 ` rsandifo at gcc dot gnu.org
2011-03-15 9:40 ` rsandifo 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-47166-4-B8AjJ2LsXK@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).