From: Mark Mitchell <mark@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
gcc-patches@gcc.gnu.org, rguenther@suse.de
Subject: Re: Make C1X anonymous structs/unions follow N1549
Date: Fri, 18 Mar 2011 22:31:00 -0000 [thread overview]
Message-ID: <4D83DD2D.5030009@codesourcery.com> (raw)
In-Reply-To: <20110318215217.GG30899@tyan-ft48-01.lab.bos.redhat.com>
On 3/18/2011 2:52 PM, Jakub Jelinek wrote:
>> This week's London WG14 meeting agreed to disallow the use of typedefs
>> in declaring anonymous structure and union fields, as per N1549. This
>> patch implements this, restricting the use of typedefs in this case to
>> -fms-extensions and -fplan9-extensions as in 4.5 and earlier releases.
> I guess it is ok for 4.6.0 too.
I think avoiding the ping-pong in behavior between 4.5 and 4.7 is a good
call. So, I think the patch is OK for 4.6.
Thank you,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2011-03-18 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 21:17 Joseph S. Myers
2011-03-18 21:52 ` Jakub Jelinek
2011-03-18 22:31 ` Mark Mitchell [this message]
2011-03-18 23:01 ` Joseph S. Myers
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=4D83DD2D.5030009@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
/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).