Re: Using LTO for Fedora package builds

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 26 February 2018 at 16:58, Zbigniew Jędrzejewski-Szmek
<zbyszek@xxxxxxxxx> wrote:
[..]
>
> > Can you repeat above and show output of the command "size /var/tmp/inst-*"?
>
> After stripping:
> 24808          /var/tmp/inst-O2
> 21060          /var/tmp/inst-O2-lto
> 22240          /var/tmp/inst-O3
> 21812          /var/tmp/inst-O3-lto
> 23256          /var/tmp/inst-Os
> 19980          /var/tmp/inst-Os-lto
>
> (24808-21060)/24808 ≈ 15%.

Zbyszek but if these sizes of the binary ELF files .. this is not what
I've been asking for :-P
ELF binary file contains many sections (check for example "objdump -h
/usr/bin/bash"), and this is why it would be better to have a look on
"size /var/tmp/inst-*" output :)

Sometimes optimisation is affecting bss and data segments sizes.
I've not been doing such comparative tests for quite long time and as
long as you have already generated some test binaries may I ask you to
show raw size or eu-size command output? :)

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux