[llvm-dev] Removing LLVM testing tools from the install distribution

[Vedant Kumar via llvm-dev]

> On May 14, 2018, at 4:14 PM, David Jones <david.jones at metrics.ca> wrote:
> 
> Please keep llvm-symbolizer in the install distribution.
> 
> If a user's program crashes then I like to print out a backtrace with file name/line number if compiled with debug. Forking off llvm-symbolizer is the easiest way for me to obtain the debug information.

Yep, at this point I'm only considering removing tools which are strictly for compiler testing.

vedant

> 
> Thanks.
> 
> 
> On Mon, May 14, 2018 at 5:27 PM, Vedant Kumar via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Should the binaries included in an LLVM release be generally useful to a wide audience of toolchain users, or is it OK to ship tools that are only really useful for LLVM development?
> 
> If the former is the case, can we consider not shipping tools which are exclusively for testing the compiler? E.g removing these 5 binaries from 5.0.2-rc1 would have saved over a hundred megabytes in uncompressed space for macOS users:
> 
> Binary name | Size in megabytes
> --------------------------------------------
> clang-check: 54.6725
> llvm-c-test: 33.8384
> clang-import-test: 20.6708
> c-index-test: 19.8632
> verify-uselistorder: 2.84348
> 
> vedant
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <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/20180515/60e8d124/attachment.html>