3 ms·
it would be good to analyze which of those .text/data sections are actually visited - i recall someone running the Vivado FPGA toolset, that is notoriously mass
by webdevver 11mo ago
it would be good to analyze which of those .text/data sections are actually visited - i recall someone running the Vivado FPGA toolset, that is notoriously massive (90GB+) over a special FUSE fs that tells you which files were accessed, and then stripping out the ones that weren't, leading ot substantial wins.
to be honest, it is surprising that a toolchain could be 350MB - that is a lot of code, if thats what it is.
- whitequark_ 11mo ago122 MB of it is Wasm machine code of a MinSizeRel LTO build of LLVM; it is compressed to 23 MB by Zstandard when your HTTP client supports that. That is about as small as you can get an LLVM/Clang/LLD bundle to be, and I put a lot of effort into making it smaller. 248 MB of it is an OpenBSD sysroot; it is compressed to 45 MB by Zstandard when your HTTP client supports that. I have not used OpenBSD and have no particular insight into what's inside.