<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 2, 2015, at 6:29 PM, Richard Smith <<a href="mailto:richard@metafoo.co.uk" class="">richard@metafoo.co.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><p dir="ltr" class="">On 2 Jun 2015 2:04 pm, "Jonathan Roelofs" <<a href="mailto:jonathan@codesourcery.com" class="">jonathan@codesourcery.com</a>> wrote:<br class="">
><br class="">
><br class="">
><br class="">
> On 6/2/15 2:38 PM, Duncan P. N. Exon Smith wrote:<br class="">
>><br class="">
>><br class="">
>>> On 2015-Jun-01, at 19:47, Chris Bieneman <<a href="mailto:beanz@apple.com" class="">beanz@apple.com</a>> wrote:<br class="">
>>><br class="">
>>>> If we drop support for building compiler-rt with GCC, this gets even simpler. Compiler-rt is *Clang's* runtime library, after all.<br class="">
>>><br class="">
>>><br class="">
>>> I don’t know if it is on the table to drop supporting compiler-rt with GCC, but that would dramatically simplify things.<br class="">
>><br class="">
>><br class="">
>> Weird, I'd assumed building compiler-rt with something other than<br class="">
>> clang was unsupported. Maybe I'm missing something, but shouldn't<br class="">
>> the only supported configuration be building with the just-built<br class="">
>> clang?<br class="">
><br class="">
><br class="">
> The current default for an in-tree build is to build compiler-rt with whatever compiler is being used to build Clang... sometimes that compiler is GCC.<br class="">
><br class="">
> I agree though. We should always use the just-built Clang, and have that behavior be opt-out (if folks need it), instead of opt-in as it is now.</p><p dir="ltr" class="">What would the build system do for a cross compile of Clang?</p></div></blockquote>This is the big question right? If we decide to only support building compiler-rt with the just-built clang that inherently means that you always have to build a clang that can run on host, so cross-compiling clang means building for host first, then the target.</div><div><br class=""></div><div>I don’t think that is the behavior we want.</div><div><br class=""></div><div>I suspect the behavior we probably want is to use the just-built clang by default unless you are cross-compiling, in which case use the host compiler.</div><div><br class=""></div><div>Whether or not the host compiler needs to be clang, or any version restrictions we want to apply is a separate issue.</div><div><br class=""></div><div>-Chris<br class=""><blockquote type="cite" class=""><div class=""><p dir="ltr" class="">><br class="">
> Jon<br class="">
><br class="">
><br class="">
>> _______________________________________________<br class="">
>> LLVM Developers mailing list<br class="">
>> <a href="mailto:LLVMdev@cs.uiuc.edu" class="">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu/" class="">http://llvm.cs.uiuc.edu</a><br class="">
>> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br class="">
>><br class="">
><br class="">
> -- <br class="">
> Jon Roelofs<br class="">
> <a href="mailto:jonathan@codesourcery.com" class="">jonathan@codesourcery.com</a><br class="">
> CodeSourcery / Mentor Embedded<br class="">
><br class="">
> _______________________________________________<br class="">
> LLVM Developers mailing list<br class="">
> <a href="mailto:LLVMdev@cs.uiuc.edu" class="">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu/" class="">http://llvm.cs.uiuc.edu</a><br class="">
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" class="">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br class="">
</p>
</div></blockquote></div><br class=""></body></html>