Re: Using LTO for Fedora package builds

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

 



On Sun, Feb 25, 2018 at 5:04 AM, Florian Weimer <fweimer@xxxxxxxxxx> wrote:
> Some packages use LTO (link-time optimization) with the GNU toolchain.
>
> In the past, this was problematic because the generated debugging
> information was not quite usable.  Today, it causes problems with some of
> the hardening quality control tooling because the annobin GCC plug-in may
> not be active when the final LTO link with new code generation happens (bug
> 1548821).
>
> What's our current take on using LTO for Fedora package builds?
>

Mir uses LTO on all platforms except ppc64 (the build dies with
undefined references on that arch (rh#1515934)). We do this because
Mir links to a lot of things inside and out and the optimizations
makes for faster and smaller libraries, which makes things better for
consumers of the Mir libraries.



-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
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