Disable macOS LTO for non-PGO (opt) builds
Categories
(Firefox Build System :: General, enhancement)
Tracking
(firefox-esr60 unaffected, firefox65 wontfix, firefox66 wontfix, firefox67 wontfix, firefox75 fixed)
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox65 | --- | wontfix |
firefox66 | --- | wontfix |
firefox67 | --- | wontfix |
firefox75 | --- | fixed |
People
(Reporter: cpeterson, Assigned: glandium)
References
Details
Attachments
(1 file)
Developers want fast local builds and try runs, so we should disable LTO in non-shipping builds (i.e. non-PGO opt and debug).
Once we have macOS PGO builds (bug 1395325), we can disable LTO for opt builds. PGO would then imply LTO, like clang-cl did on Windows in bug 1475660.
Would we want to disable LTO for opt builds in all branches (autoland, inbound, central, and try) or just on autoland, inbound, and try? Is there value in building and testing opt with LTO in central in addition to opt without LTO on autoland and inbound? Any bugs we find in one of those configurations but not the other is most likely a compiler bug, not a Firefox bug. Do we care?
Comment 1•5 years ago
|
||
I'm reasonably sure we only LTO shippable builds, is the right glandium?
Assignee | ||
Comment 2•5 years ago
|
||
We're still manually enabling LTO on opt mac builds on automation. See browser/config/mozconfigs/macosx64/nightly
, browser/config/mozconfigs/macosx64/devedition
, browser/config/mozconfigs/macosx64/beta
and browser/config/mozconfigs/macosx64/release
. Which means it's enabled on shippable builds and opt builds.
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Now that shippable macOS builds have PGO+LTO enabled, it is not
necessary to build the normal macOS builds with LTO enabled.
Comment 4•5 years ago
|
||
Thanks for taking this. Completely slipped my mind.
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Description
•