[cfe-dev] Linking ProfileRT when using -nodefaultlibs

[Eric Fiselier]

> Didn't realized we even supported using GCC to build libc++.

I think we should *try* to support the same compilers as LLVM does (minus
anything windows related).
That way less problems will arise when people build LLVM w/ libc++ in tree.
However I'm not sure how feasible that is and would like some input from
others.

> I thought that gcc already supported -nostdlib++ and we only had these
convolutions because clang didn't...

I can't find any documentation on that.

/Eric



On Mon, Nov 10, 2014 at 12:56 PM, David Chisnall <
David.Chisnall at cl.cam.ac.uk> wrote:

> On 10 Nov 2014, at 19:40, Eric Fiselier <eric at efcs.ca> wrote:
>
> > > The reason we use -nodefaultlibs is to avoid linking the system's
> libc++. There's a -nostdinc++, maybe there should be a -nostdlib++? Or
> perhaps -stdlib=none?
> > -nostdlib already exists but it acts like -nodefaultlibs and it drops
> the startup files as well.
> > I would support -stdlib=none but I'm hesitant to start depending on
> Clang only flags. It would be nice to not have to special case GCC.
> >
>
> I thought that gcc already supported -nostdlib++ and we only had these
> convolutions because clang didn't...
>
> David
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20141110/83aba270/attachment.html>