From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jason Merrill <jason@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ RFC / Patch] Again about PR 70202
Date: Fri, 10 Jun 2016 20:30:00 -0000 [thread overview]
Message-ID: <575B2372.6020806@oracle.com> (raw)
In-Reply-To: <CADzB+2nPhiBWPCkNiieaj++YH82Rg=wgvQ4oHrFZPxnNh128kw@mail.gmail.com>
.. the type of b1 becomes error_mark_node at the end of start_decl as
an effect of start_decl_1 (which issues the incomplete type error).
Paolo.
next prev parent reply other threads:[~2016-06-10 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 17:02 Paolo Carlini
2016-06-09 17:06 ` Jakub Jelinek
2016-06-09 21:39 ` Jason Merrill
2016-06-09 23:29 ` Paolo Carlini
2016-06-10 1:43 ` Paolo Carlini
2016-06-10 20:09 ` Jason Merrill
2016-06-10 20:15 ` Paolo Carlini
2016-06-10 20:30 ` Paolo Carlini [this message]
2016-06-10 20:34 ` Paolo Carlini
2016-06-10 20:48 ` Paolo Carlini
2016-06-11 16:06 ` [C++ Patch] PR 70202: avoid creating incomplete types (was: "[C++ RFC / Patch] Again about PR 70202") Paolo Carlini
2016-06-14 13:06 ` [C++ Patch] PR 70202: avoid creating incomplete types Jason Merrill
2016-06-14 18:09 ` Paolo Carlini
2016-06-14 19:29 ` 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=575B2372.6020806@oracle.com \
--to=paolo.carlini@oracle.com \
--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).