From: Ian Lance Taylor <iant@google.com>
To: Romain Geissler <romain.geissler@gmail.com>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: PATCH RFA: Build stages 2 and 3 with C++
Date: Mon, 08 Aug 2011 18:49:00 -0000 [thread overview]
Message-ID: <mcrei0veo2m.fsf@coign.corp.google.com> (raw)
In-Reply-To: <275E76F7-69B1-408C-9DC6-2C08BDBB5036@gmail.com> (Romain Geissler's message of "Mon, 8 Aug 2011 19:42:34 +0200")
Romain Geissler <romain.geissler@gmail.com> writes:
> This new build behavior broke former plugins built with gcc. Indeed,
> all cc1 function symbols are now mangled and thus with the current
> trunk, plugins should also look for mangled symbols (and so built
> with g++).
>
> What's the new GCC policy about that ? Do plugins have to be built
> using g++ only, or does the plugin developer have the choice to
> use both gcc and g++ according to it's need (at the cost of adding
> extern "C" {…} in almost every headers to forbid mangling) ?
I think that ideally we would have a well-defined plugin interface,
plugins would stick to calling that, and that interface would be a C
interface. (I see that gcc-plugin.h does already provide a C interface
even when gcc is compiled with C++.)
However, since we currently permit plugins to call anything in gcc, I
think the answer is going to have to be that plugins which do that
should be compiled with C++. I don't think that adding extern "C" to
all gcc header files is the right approach. Adding extern "C" to a few
selected header files seems fine.
Ian
next prev parent reply other threads:[~2011-08-08 18:49 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 6:56 Ian Lance Taylor
2011-07-16 7:05 ` Andrew Pinski
2011-07-16 7:48 ` Ian Lance Taylor
2011-07-16 7:59 ` Basile Starynkevitch
2011-07-17 3:17 ` Ian Lance Taylor
2011-07-16 16:11 ` Diego Novillo
2011-07-16 22:58 ` Ian Lance Taylor
2011-07-17 10:36 ` Richard Guenther
2011-07-17 12:21 ` Eric Botcazou
2011-07-17 16:55 ` Richard Guenther
2011-07-17 17:55 ` Markus Trippelsdorf
2011-07-17 22:37 ` Markus Trippelsdorf
2011-09-04 17:20 ` Thomas Schwinge
2011-07-16 20:40 ` Toon Moene
2011-07-19 21:33 ` Ian Lance Taylor
2011-07-19 22:24 ` Gabriel Dos Reis
2011-07-20 0:46 ` H.J. Lu
2011-07-20 1:15 ` H.J. Lu
2011-07-20 6:28 ` David Edelsohn
2011-07-20 9:34 ` Jonathan Wakely
2011-07-20 11:02 ` Jonathan Wakely
2011-07-20 12:41 ` David Edelsohn
2011-07-20 12:48 ` Richard Guenther
2011-07-20 14:07 ` Diego Novillo
2011-07-20 14:34 ` Ian Lance Taylor
2011-07-20 15:35 ` Jonathan Wakely
2011-07-20 15:06 ` Toon Moene
2011-07-20 15:23 ` Ian Lance Taylor
2011-07-20 15:53 ` David Edelsohn
2011-07-20 15:55 ` Ian Lance Taylor
2011-07-20 20:05 ` David Edelsohn
2011-07-20 20:53 ` Ian Lance Taylor
2011-07-20 21:06 ` Mike Stump
2011-07-21 0:10 ` Ian Lance Taylor
2011-07-21 9:40 ` Basile Starynkevitch
2011-07-21 16:06 ` Ian Lance Taylor
2011-07-21 17:44 ` Jakub Jelinek
2011-07-21 19:40 ` Ian Lance Taylor
2011-07-21 20:12 ` Basile Starynkevitch
2011-07-21 22:38 ` Ian Lance Taylor
2011-07-21 6:57 ` David Edelsohn
2011-07-21 7:25 ` Eric Botcazou
2011-07-21 14:24 ` David Edelsohn
2011-07-20 17:58 ` Thomas Schwinge
2011-07-20 21:41 ` Toon Moene
2011-07-31 23:20 ` Marc Glisse
2011-08-01 9:14 ` Richard Guenther
2011-08-01 9:53 ` Joseph S. Myers
2011-08-01 9:59 ` Richard Guenther
2011-08-01 10:05 ` Marc Glisse
2011-08-08 17:42 ` Romain Geissler
2011-08-08 18:49 ` Ian Lance Taylor [this message]
2011-08-08 19:40 ` Romain Geissler
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=mcrei0veo2m.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=romain.geissler@gmail.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).