From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7027 invoked by alias); 22 Apr 2011 16:59:10 -0000 Received: (qmail 7018 invoked by uid 22791); 22 Apr 2011 16:59:09 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from qmta02.emeryville.ca.mail.comcast.net (HELO qmta02.emeryville.ca.mail.comcast.net) (76.96.30.24) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 Apr 2011 16:58:48 +0000 Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta02.emeryville.ca.mail.comcast.net with comcast id afpc1g0061Y3wxoA2gyo29; Fri, 22 Apr 2011 16:58:48 +0000 Received: from up.mrs.kithrup.com ([24.4.193.8]) by omta15.emeryville.ca.mail.comcast.net with comcast id agym1g00r0BKwT48bgynSd; Fri, 22 Apr 2011 16:58:47 +0000 Subject: Re: [PATCH PING] c++-specific bits of tree-slimming patches Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Mike Stump In-Reply-To: <4DB1A4D4.6020500@redhat.com> Date: Fri, 22 Apr 2011 17:35:00 -0000 Cc: Nathan Froyd , gcc-patches@gcc.gnu.org, Alexandre Oliva Content-Transfer-Encoding: quoted-printable Message-Id: References: <20110324131518.GO23480@codesourcery.com> <4D9F4AE0.6050200@redhat.com> <20110422005052.GU23480@codesourcery.com> <4DB0ECA1.7080705@redhat.com> <20110422025554.GV23480@codesourcery.com> <4DB10B29.9040407@redhat.com> <4DB1A4D4.6020500@redhat.com> To: Jason Merrill X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-04/txt/msg01878.txt.bz2 On Apr 22, 2011, at 8:55 AM, Jason Merrill wrote: > On 04/22/2011 02:13 AM, Mike Stump wrote: >> http://gcc.gnu.org/ml/gcc/2005-04/msg00161.html >>=20 >> has the details of why the code was put in. >=20 > Right. At the time, we were sorting the goto queue based on pointer valu= es, which caused the problem. We no longer do that, Excellent. That was the only concern I knew of.