all: understand binary size changes vs 1.14 #38694
I was curious about binary size changes from 1.14 to tip. The results:
This immediately raises a few questions.
There may not be any bugs here, but it'd be nice to understand a bit better what happened.
Anybody up for doing some sleuthing?
Of note for anyone investigating, you'll discover that object files are ~50% bigger at tip than 1.14. This is due to the -newobj flag being enabled by default. If you're going to use object files to investigate, you probably want to disable it.
The text was updated successfully, but these errors were encountered:
Just to be clear, when you list this line:
link 6613720 6755112 +141392 +2.138%
This is comparing 1.15 linker sources built with 1.15 toolchain, vs 1.14 sources built with 1.14 toolchain, correct?
I spent a little time looking at the specific case of the linker. From objdump -h it looks as though the size increase is spread out across many sections (text, pclntab, dwarf, etc) as opposed to being just in one or two sections.