public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Mike Stump <mikestump@comcast.net>
Cc: Nathan Froyd <froydnj@codesourcery.com>,
	gcc-patches@gcc.gnu.org,
	       Alexandre Oliva <aoliva@redhat.com>
Subject: Re: [PATCH PING] c++-specific bits of tree-slimming patches
Date: Fri, 22 Apr 2011 16:59:00 -0000	[thread overview]
Message-ID: <4DB1A4D4.6020500@redhat.com> (raw)
In-Reply-To: <D5C757DC-3A75-424D-886F-0FC7E54EDDDB@comcast.net>

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?

Jason


  parent reply	other threads:[~2011-04-22 15:55 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 [this message]
2011-04-22 17:35               ` Mike Stump
2011-04-29  8:38               ` Alexandre Oliva
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=4DB1A4D4.6020500@redhat.com \
    --to=jason@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).