Closed Bug 1293403 Opened 9 years ago Closed 5 months ago

stylo: Check what the status of LTO for our release builds is.

Categories

(Core :: CSS Parsing and Computation, defect, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1486042
Tracking Flags:
Tracking Status
firefox57 --- wontfix

People

(Reporter: emilio, Unassigned)

References

(Blocks 1 open bug)

Details

We should take a look, if we are able to get our FFI calls inlined, that'd be a win in runtime performance, as well as possibly in code size (though a lighter one arguably).
Priority: -- → P3
Priority: P3 → P4
Emilio, do we need to do anything to enable LTO for Stylo code? Or is this bug just about verifying the current output of LTO code?
No longer blocks: stylo
Flags: needinfo?(emilio)
Well, this was about being able to inline FFI calls, which AIUI is just not possible with MSVC, and would be a significant effort building FF with clang. So there's a bunch of work to do here if we want to make this doable, but we figured out other solutions at the potential perf issues that we were facing a year ago. Still would be nice, of course.
Flags: needinfo?(emilio)
status-firefox57=wontfix unless someone thinks this bug should block 57
status-firefox57: --- → wontfix
Severity: normal → S3

Is this a duplicate of bug 1486042?

Yeah

Status: NEW → RESOLVED
Closed: 5 months ago
Duplicate of bug: 1486042
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.