The case of LTO when produced enlarged binaries

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

 



Hi. In rare cases building packages with LTO producing binaries or libraries which have bigger size then if they have built without LTO. For example 'kitty' package:

* with LTO:
  - koji task https://koji.fedoraproject.org/koji/taskinfo?taskID=47762998
    1.79 MB glfw-wayland.so
    1.99 MB glfw-x11.so
    4.78 MB fast_data_types.so
    8.56 MB total

* no LTO
  - koji https://koji.fedoraproject.org/koji/taskinfo?taskID=47769854
    1.65 MB glfw-wayland.so
    1.84 MB glfw-x11.so
    4.51 MB fast_data_types.so
    8.00 MB total

Difference is 7%. What we should do in such case? Should we disable LTO for such packages? Or there is still could be gains from faster code execution speed?
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [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