Is there an expected percent increase in binary size with ASan? Over a set of a few thousand unit test binaries, I'm seeing some pretty significant size increases (compilation with -O0 and debug info, with dynamically linked asan dylib, on darwin):
50% of ASan executables are at least 183.25% the size of the non-ASan version. 10% of ASan executables are at least 276.53% the size of the non-ASan version. 5% of ASan executables are at least 332.92% the size of the non-ASan version. This seems like pretty significant bloat to me - is it expected? And are there any methods you suggest for reducing the size? I would expect some increase in size from instrumentation, but a median increase of 180% seems like quite a lot. Francis -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
