From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH to implement mangling of unnamed types with linkage
Date: Sun, 23 Jan 2011 22:49:00 -0000 [thread overview]
Message-ID: <AANLkTinw0R24--bzGy7DxPK56rXa8uPO-irLMj6WPLDc@mail.gmail.com> (raw)
In-Reply-To: <4AC69F84.7040305@redhat.com>
On Fri, Oct 2, 2009 at 5:49 PM, Jason Merrill <jason@redhat.com> wrote:
> DR 757 allows types without linkage to be used in decls with linkage so long
> as those decls are defined in the current translation unit. And in fact
> some of those types really do have linkage: notably, class-scope unnamed
> types and function-local types in functions with vague linkage. The C++ ABI
> now specifies a mangling for these, which this patch implements.
>
> Tested x86_64-pc-linux-gnu, applied to trunk.
>
This caused:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47049
--
H.J.
prev parent reply other threads:[~2011-01-23 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 0:49 Jason Merrill
2011-01-23 22:49 ` H.J. Lu [this message]
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=AANLkTinw0R24--bzGy7DxPK56rXa8uPO-irLMj6WPLDc@mail.gmail.com \
--to=hjl.tools@gmail.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).