public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jason Merrill <jason@redhat.com>, Adam Butcher <adam@jessamine.co.uk>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR c++/65750
Date: Wed, 24 Jun 2015 10:58:00 -0000	[thread overview]
Message-ID: <558A8CA0.9090401@oracle.com> (raw)
In-Reply-To: <552D87F8.90005@redhat.com>

Hi,

On 04/14/2015 11:34 PM, Jason Merrill wrote:
> On 04/14/2015 05:27 PM, Adam Butcher wrote:
>> On 2015-04-10 15:57, Adam Butcher wrote:
>>> +          cp_lexer_consume_token (parser->lexer);
>>
>> Actually there should be two of these as the 'auto' isn't consumed yet.
> OK.

I'm finishing retesting the amended patch and, if everything goes well, 
I will apply it to trunk, as approved by Jason (only additional minor 
tweak: testcase in cpp0x instead of cpp1y).

What about gcc-5-branch? It's a regression.

Thanks,
Paolo.

  reply	other threads:[~2015-06-24 10:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 21:01 Adam Butcher
2015-04-14 21:27 ` Adam Butcher
2015-04-14 21:34   ` Jason Merrill
2015-06-24 10:58     ` Paolo Carlini [this message]
2015-06-26 22:36       ` 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=558A8CA0.9090401@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=adam@jessamine.co.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).