From: Alexandre Oliva <aoliva@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Mike Stump <mikestump@comcast.net>,
Nathan Froyd <froydnj@codesourcery.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH PING] c++-specific bits of tree-slimming patches
Date: Fri, 29 Apr 2011 08:38:00 -0000 [thread overview]
Message-ID: <orpqo5o5o5.fsf@livre.localdomain> (raw)
In-Reply-To: <4DB1A4D4.6020500@redhat.com> (Jason Merrill's message of "Fri, 22 Apr 2011 11:55:00 -0400")
On Apr 22, 2011, Jason Merrill <jason@redhat.com> wrote:
> On 04/22/2011 02:13 AM, Mike Stump wrote:
>> http://gcc.gnu.org/ml/gcc/2005-04/msg00161.html
>>
>> has the details of why the code was put in.
> Right. At the time, we were sorting the goto queue based on pointer
> values, which caused the problem. We no longer do that, so we
> shouldn't need this workaround (deferring creation of case label
> labels) anymore.
> What do you think, Alex?
Yeah, this change looks safe now.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
next prev parent reply other threads:[~2011-04-29 7:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 13:15 Nathan Froyd
2011-04-05 12:10 ` Nathan Froyd
2011-04-08 17:50 ` Jason Merrill
2011-04-14 11:30 ` Nathan Froyd
2011-04-14 11:32 ` Richard Guenther
2011-04-21 16:33 ` Joseph S. Myers
2011-04-22 2:49 ` Nathan Froyd
2011-04-22 3:59 ` Jason Merrill
2011-04-22 4:22 ` Nathan Froyd
2011-04-22 8:57 ` Jason Merrill
2011-04-22 9:12 ` Mike Stump
2011-04-22 12:36 ` Richard Guenther
2011-04-22 14:45 ` Nathan Froyd
2011-04-22 16:59 ` Jason Merrill
2011-04-22 17:35 ` Mike Stump
2011-04-29 8:38 ` Alexandre Oliva [this message]
2011-04-25 23:06 ` Nathan Froyd
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=orpqo5o5o5.fsf@livre.localdomain \
--to=aoliva@redhat.com \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=mikestump@comcast.net \
/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).