[llvm-dev] New LLVM git repository conversion prototype

[Jonas Hahnfeld via llvm-dev]

+1 to David's motivation and this has been brought up quite some times 
in the past.
As another data point the OpenMP runtimes can be used with both GCC and 
Intel Compiler. With the current git mirror 
(https://github.com/llvm-mirror/openmp), a full clone is as small as 
~20MB. However, I didn't have time to experiment with sparse checkouts 
or other techniques with this prototype so I can't say how much you 
really get in case you only want openmp...

Jonas

On 2018-10-18 15:46, Renato Golin via llvm-dev wrote:
> On Thu, 18 Oct 2018 at 14:19, David Chisnall via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> I would still prefer that projects that are not tightly coupled to 
>> LLVM (lib*, pstl, compiler-rt) be in separate repositories.  These do 
>> not link against LLVM libraries, are not version locked to any given 
>> LLVM / clang / whatever release, and most of them need to support 
>> multiple LLVM releases, so there is little benefit to having them in 
>> the monorepo and there is a disadvantage for people wishing to use and 
>> contribute to them independent of the rest of LLVM.
> 
> This sounds like:
> 
> Mono-repo:
> 
>>   * cfe -> clang
>>   * clang-tools-extra
>>   * llvm
>>   * llgo ??
> 
> Separate - Core Libs (4 repos or all-in-one?):
> 
>>   * compiler-rt
>>   * libcxx
>>   * libcxxabi
>>   * libunwind
> 
> Separate - Other Libs (each in own repo):
> 
>>   * libclc ?? (in mono?)
>>   * polly ?? (in mono?)
>>   * openmp
>>   * parallel-libs
>>   * pstl
> 
> Separate - Tools (each in own repo):
> 
>>   * lld
>>   * lldb
> 
> Separate - Others:
> 
>>   * debuginfo-tests ??
> 
> Archive:
> 
>>   * stacker (deleted after r40406)
>>   * dragonegg (also "gcc-plugin", the original name)
>>   * poolalloc
>>   * safecode