search for: minsizerelease

i want to integrate a C source JITer into my application but the resulting executables are too large is it possible to reduce the resulting libs/exe some way? current VS2017/svn build example: llvm-build\Release\bin\clang-interpreter.exe ~36MB for now (that can change later) - i want to jit simple c-code - no std library or something - x64 only - no deep/full architecture optimization needed -

...eak the LLVM tests, nor introduce loads of private changes to our branch. I know our test/QA team have been doing some analysis using Bloaty McBloatFace to see exactly where the size is coming from and produced some really nice visualizations of that data. They've also been looking at how the MinSizeRelease config does on Windows. I think the size savings were decent but I'm not sure of performance numbers, if they have any yet. I'll ask around at what we have to share once back in the office. Thanks for sharing your data! -Greg On Sat, 17 Mar 2018 at 12:36, Dimitry Andric via cfe-dev &l...

...duce loads of private changes > to our branch. > > I know our test/QA team have been doing some analysis using Bloaty > McBloatFace to see exactly where the size is coming from and produced some > really nice visualizations of that data. They've also been looking at how > the MinSizeRelease config does on Windows. I think the size savings were > decent but I'm not sure of performance numbers, if they have any yet. > > I'll ask around at what we have to share once back in the office. > > Thanks for sharing your data! > > -Greg > > > > On Sat, 17...

Hi all, I recently did a run where I built clang executables on FreeBSD 12-CURRENT [1], from trunk r250000 (2015-10-11) all through r327700 (2018-03-16), with increments of 100 revisions. This is mainly meant as an archive, for easily doing bisections, but there are also some interesting statistics. From r250000 through r327700: * the total (stripped) executable size grew by approximately 43% *

...VM tests, nor introduce loads of private changes to our branch. > > I know our test/QA team have been doing some analysis using Bloaty McBloatFace to see exactly where the size is coming from and produced some really nice visualizations of that data. They've also been looking at how the MinSizeRelease config does on Windows. I think the size savings were decent but I'm not sure of performance numbers, if they have any yet. > > I'll ask around at what we have to share once back in the office. > > Thanks for sharing your data! > > -Greg > > > > On Sat,...

...anges >> to our branch. >> >> I know our test/QA team have been doing some analysis using Bloaty >> McBloatFace to see exactly where the size is coming from and produced some >> really nice visualizations of that data. They've also been looking at how >> the MinSizeRelease config does on Windows. I think the size savings were >> decent but I'm not sure of performance numbers, if they have any yet. >> >> I'll ask around at what we have to share once back in the office. >> >> Thanks for sharing your data! >> >> -Greg &g...