From: Ian Lance Taylor <iant@google.com>
To: Marc Glisse <marc.glisse@inria.fr>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Ping: demangle C++ extern "C" functions
Date: Sat, 22 Oct 2011 17:51:00 -0000 [thread overview]
Message-ID: <mcr1uu5kqam.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1110220827580.2327@laptop-mg.saclay.inria.fr> (Marc Glisse's message of "Sat, 22 Oct 2011 09:06:00 +0200 (CEST)")
Marc Glisse <marc.glisse@inria.fr> writes:
> g++ doesn't currently generate those, but I would like to change that
> (c++/2316). And nothing prevents another compiler from actually
> implementing the itanium C++ ABI (this code is mostly for binutils if
> I understand correctly).
>
> I thought it made sense to submit independent pieces first, but if it
> is preferable to wait until everything is ready (not soon) I
> understand.
Independent pieces is fine. I just wanted to make sure there was some
reason for it.
Ian
prev parent reply other threads:[~2011-10-22 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 21:05 Marc Glisse
2011-10-21 19:29 ` Ping: " Marc Glisse
2011-10-22 5:54 ` Ian Lance Taylor
2011-10-22 8:03 ` Marc Glisse
2011-10-22 17:51 ` Ian Lance Taylor [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=mcr1uu5kqam.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marc.glisse@inria.fr \
/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).