public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Nathan Froyd <froydnj@codesourcery.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	Gerald Pfeifer <gerald@pfeifer.com>,
	       Jack Howarth <howarth@bromo.med.uc.edu>,
	       Janis Johnson <janisjo@codesourcery.com>,
	gcc-patches@gcc.gnu.org,
	       Richard Guenther <richard.guenther@gmail.com>,
	jason@redhat.com
Subject: Re: [PATCH][4.6] detect C++ errors to fix 2288 and 18770
Date: Thu, 26 May 2011 18:24:00 -0000	[thread overview]
Message-ID: <1306431509.25125.111.camel@otta> (raw)
In-Reply-To: <20110526012420.GA15460@nightcrawler>

On Wed, 2011-05-25 at 21:24 -0400, Nathan Froyd wrote:
> On Wed, May 25, 2011 at 03:22:07PM -0400, Nathan Froyd wrote:
> > The patch just requires some shuffling of logic to catch issues now;
> > below is a version that works for me on the trunk.
> > 
> > This new checking does require modifying g++.dg/cpp0x/range-for5.C.
> > 
> > Tested with g++ testsuite on x86_64-unknown-linux-gnu; tests in progress
> > for libstdc++.  OK to commit?
> 
> Below is a slightly revised patch that actually adds all the necessary
> dg-error directives to range-for5.C.  Tested the same way; Peter Bergner
> was kind enough to bootstrap and test the previous patch on
> powerpc64-linux-gnu with (almost) clean results as well.

FYI, the revised patch passes bootstrap and regtesting (-m32 and -m64) with
no regressions on powerpc64-linux.

Peter



  reply	other threads:[~2011-05-26 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 21:39 Janis Johnson
2010-05-05  2:32 ` Jason Merrill
2011-05-22 21:24 ` Jack Howarth
2011-05-23  7:13   ` Gerald Pfeifer
2011-05-23  8:34     ` H.J. Lu
2011-05-25 19:57       ` Nathan Froyd
2011-05-26  8:11         ` Nathan Froyd
2011-05-26 18:24           ` Peter Bergner [this message]
2011-05-26 19:17           ` Jason Merrill

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=1306431509.25125.111.camel@otta \
    --to=bergner@vnet.ibm.com \
    --cc=froydnj@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=hjl.tools@gmail.com \
    --cc=howarth@bromo.med.uc.edu \
    --cc=janisjo@codesourcery.com \
    --cc=jason@redhat.com \
    --cc=richard.guenther@gmail.com \
    /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).