This is the mail archive of the
mailing list for the GCC project.
Re: gcc-in-cxx branch created
- From: "Gabriel Dos Reis" <gdr at integrable-solutions dot net>
- To: "Ian Lance Taylor" <iant at google dot com>
- Cc: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Thu, 19 Jun 2008 05:47:27 -0500
- Subject: Re: gcc-in-cxx branch created
- References: <firstname.lastname@example.org>
On Wed, Jun 18, 2008 at 1:01 AM, Ian Lance Taylor <email@example.com> wrote:
> As I promised at the summit today, I have created the branch
> gcc-in-cxx (I originally said gcc-in-c++, but I decided that it was
> better to avoid possible meta-characters). The goal of this branch is
> to develop a version of gcc which is compiled with C++. Here are my
> presentation slides in PDF format: http://airs.com/ian/cxx-slides.pdf .
Excellent slides. Many thanks for doing this.
> I have not yet committed any patches to the branch--at present it is
> just a copy of the trunk. I will start committing patches soon, and
> anybody else may submit patches as well. The branch will follow the
> usual gcc maintainership rules, except that any non-algorithmic
> maintainer may additionally approve or commit patches which permit
> compilation with C++.
I have a question: I suspect that in concreteness you would prefer declarations
in GCC headers have a C++ linkage, as opposed to C linkage -- except where
for interoperability with common runtime systems, we want the
declarations to have
C linkage (e.g. in libgcc for example). Am I correct?
The reason I'm asking is that a fresh build o gcc-in-cxx dies on my machine with
complains that `program' has conflicting declarations: once in
libcpp.h as having
C++ linkage, once in toplev.h with a C declaration. It is the
tradition in modern
C++ to avoid having many `sources' for the same declaration.