[llvm-dev] New LLVM git repository conversion prototype

[Rui Ueyama via llvm-dev]

On Thu, Oct 18, 2018 at 6:46 AM Renato Golin via llvm-dev <
llvm-dev at lists.llvm.org> 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
>

lld should be in the monorepo because lld is linked against LLVM (for LTO)
and tightly coupled with LLVM as clang is with LLVM. We often submit
patches both to LLVM and lld to make incompatible changes.

Separate - Others:
>
> >   * debuginfo-tests ??
>
> Archive:
>
> >   * stacker (deleted after r40406)
> >   * dragonegg (also "gcc-plugin", the original name)
> >   * poolalloc
> >   * safecode
>
> --
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181022/644959fd/attachment.html>