fdeazeve added a comment. In D141381#4040639 <https://reviews.llvm.org/D141381#4040639>, @probinson wrote:
> To get data about the code size impact, people typically build some large > codebase with/without their patch and compare the .text sizes. It's common to > use clang itself for this experiment. I ran a couple of experiments (*), running `objdump --section-headers build/bin/clang | grep text`: Debug without patch: 178,707,948 bytes Debug with patch: 178,785,896 bytes (+0.04%) Release without patch: 85,734,800 bytes Release with patch: 85,734,800 bytes (no diff) (*) Baseline commit for the compiler == d74e36572a51 <https://reviews.llvm.org/rGd74e36572a5110b388fcbc6188dabdfffc18fe4f>, patch was applied on top of it. The clang used in these experiments was built from commit 304838e828f9 Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D141381/new/ https://reviews.llvm.org/D141381 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
