llvm dev - Jun 2016 - [RFC] LLVM Directory Structure Changes (was Re: [PATCH] D20992: [CMake] Add LLVM runtimes directory)

On 9 June 2016 at 18:49, Justin Bogner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> This all seems pretty sensible. Should we also use the opportunity to
> split compiler-rt's builtins and profiling/sanitizer/etc runtimes,
since
> we'll be moving things around anyway?
Also be good to make Compiler-RT and libc++ cross-compile for multiple
targets... :/

While that may be another battle entirely, it'd be good to keep that
in mind if we do split them up to pieces.

cheers,
--renato

> On Jun 9, 2016, at 10:53 AM, Renato Golin <renato.golin at
linaro.org> wrote:
> 
> On 9 June 2016 at 18:49, Justin Bogner via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> This all seems pretty sensible. Should we also use the opportunity to
>> split compiler-rt's builtins and profiling/sanitizer/etc runtimes,
since
>> we'll be moving things around anyway?
> 
> Also be good to make Compiler-RT and libc++ cross-compile for multiple
> targets... :/
Yes, that is part of the eventual goal for this. I *really* want to be able to
build a full cross-compiler and runtime stack from a single CMake invocation.
Ideally supporting /n/ targets.

I have lots of ideas in this area, but it is being kept in mind.

-Chris
> 
> While that may be another battle entirely, it'd be good to keep that
> in mind if we do split them up to pieces.
> 
> cheers,
> --renato

On 9 June 2016 at 19:13, Chris Bieneman <beanz at apple.com>
wrote:
>> On 9 June 2016 at 18:49, Justin Bogner via llvm-dev
>> <llvm-dev at lists.llvm.org> wrote:
>>> This all seems pretty sensible. Should we also use the opportunity
to
>>> split compiler-rt's builtins and profiling/sanitizer/etc
runtimes, since
>>> we'll be moving things around anyway?
>>
>> Also be good to make Compiler-RT and libc++ cross-compile for multiple
>> targets... :/
>
> Yes, that is part of the eventual goal for this. I *really* want to be able
to build a full cross-compiler and runtime stack from a single CMake invocation.
Ideally supporting /n/ targets.
>
> I have lots of ideas in this area, but it is being kept in mind.
Thanks Chris,

A big odd user of RT is Android, and they're having a lot of trouble
cross-compiling, so they ended up creating their own build system.

I'm copying Steve that has had more than his share of problems, maybe
a sync on how we both want to compile RT wouldn't hurt.

My goal is to get Android compiling RT together with Clang in the
exact same way we do, so we only need to maintain one toolchain.

cheers,
--renato