https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67590
Christer Solskogen changed:
What|Removed |Added
CC||christer.solskogen at gmail
dot co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97637
Christer Solskogen changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97637
--- Comment #4 from Christer Solskogen ---
Okay, so LTO together with O2/O3 or Ofast will not help code size that much.
I was worried that something was wrong with how GCC was configured or the
command line parameters I was using since the binar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97637
--- Comment #2 from Christer Solskogen ---
You are correct. I've replaced Ofast with O2 (but it doesn't seem to matter
that much) - with the default inline-unit-growth the binary gets 5% bigger.
With inline-unit-growth=20 the binary gets 5%~ sma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97637
Bug ID: 97637
Summary: Compiling with LTO causes a bigger binary
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
