[llvm-dev] PSA: the future of compiler-rt’s Scudo

Chandler Carruth via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 15 14:39:58 PST 2019

I don't think this is the thread to re-litigate this. We have plenty of
examples in both directions, and we should instead focus on evaluating how
well technical approaches to minimize the cost on standalone runtime
libraries like this are effective with the prototype monorepo and whether
that is adequate.

On Tue, Jan 15, 2019 at 2:41 AM David Chisnall via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On 14/01/2019 21:56, Kostya Kortchinsky via llvm-dev wrote:
> > An early plan was to move to our own googlesource repository (or the
> > like), but Chandler suggested we stay in compiler-rt, as a separate
> > directory that could be a slice of the new git monorepo. This appeared
> > to be acceptable to everybody involved (Chandler, Kostya S., Petr,
> > Roland, Julia), and is now the plan of record. Once the standalone
> > version is in, the non-standalone Scudo will likely be deprecated,
> > although this part hasn’t been formalized yet.
> So now we have a project that is loosely coupled to LLVM, can be built
> without any other parts of LLVM, can be built as part of another shared
> library that takes no dependencies on LLVM, will have contributors that
> do not contribute to the rest of LLVM, but requires a clone of the
> entire LLVM project to be able to access?
> This is precisely the use case that caused many objections to the
> everything-in-the-monorepo model.
> David
> _______________________________________________
> 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/20190115/742de881/attachment.html>

More information about the llvm-dev mailing list