This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: LLVM/GCC Integration Proposal

From: Devang Patel <devang dot patel at gmail dot com>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: Chris Lattner <clattner at apple dot com>, GCC Development <gcc at gcc dot gnu dot org>, Chris Lattner <sabre at nondot dot org>
Date: Sat, 19 Nov 2005 14:40:22 -0800
Subject: Re: LLVM/GCC Integration Proposal
References: <37A3A6DD-711A-4856-ACC0-259FCD9841CF@apple.com> <Pine.LNX.4.64.0511191105480.19624@digraph.polyomino.org.uk>

On 11/19/05, Joseph S. Myers <joseph@codesourcery.com> wrote:
> On Fri, 18 Nov 2005, Chris Lattner wrote:
>
> > 1. The build system is taught about C++ code.
>
> With toplevel bootstrap this will bootstrap libstdc++ so that the compiler
> ends up linked with the new libstdc++ not the (in general
> ABI-incompatible) old one?  (This question applies to all projects
> involving C++ in GCC.)

In apple-local-200502-branch, if you bootstrap compiler using
build_gcc (this is what we do here) then it does not build libstdc++
at all. Here at Apple, libstdc++ is built as a separate  project. This
has nothing to do with llvm.

-
Devang

References:
- LLVM/GCC Integration Proposal
  - From: Chris Lattner
- Re: LLVM/GCC Integration Proposal
  - From: Joseph S. Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]