[LLVMdev] [cfe-dev] RFC: A proposal to move toward using C++11 features in LLVM & Clang / bounding support for old host compilers

[Richard Smith]

On Mon, Oct 28, 2013 at 5:13 PM, "C. Bergström" <cbergstrom at pathscale.com>wrote:

> On 10/29/13 07:01 AM, Richard Smith wrote:
>
>>
>> [As an aside: I use libc++ for my Clang development (on Ubuntu Linux),
>> and it works for me (tm). This is with libstdc++ providing the ABI pieces,
>> rather than libc++abi or libcxxrt, though.]
>>
> libc++ "works" for us as well, but it can't self host. I don't know if
> your "works" and my definition of works is 1:1. Can your clang+libc++ build
> itself multiple levels deep?
>

Yes. I use my system g++ for my stage1, I use that compiler to build my
stage2, and I use my stage2 bootstrapped compiler for all my development
work. I rebuild my stage2 every few months.

I don't think I've ever explicitly checked that I get stage2 == stage3, but
stage2 produces working compilers, but I'm doing a full bootstap now and
I'll let you know when it's done.


> I believe both ABI alternatives are drop-in replacements and I hope not
> the root cause of what we observed. (We are only testing with libcxxrt
> though)
> --------------
> I could totally be wrong about libc++ and it's "our" fault in the testing
> we've done. I apologize if this is a non-issue and I hope during the "heads
> up" phase we have time to actually interject if there are potentially fatal
> issues. Forcing a dependency on gnu runtime/libs/STL is a serious
> regression imho.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131028/102440bc/attachment.html>