News for hackers. Stuff that matters.
Re:Chrome just got faster with Profile Guided Optimization by mintplant on Tuesday August 25, 2020 @01:56PM (#24274039)
You can pass a PGO flag to the build system [0], but IIRC from when I was there last, Mozilla puts some serious machine hours into PGO cycles for each release and that isn't easy to replicate as an individual developer. The profiling captures things which are very specific to the actual build being optimized, so inlining that information into the codebase wouldn't be so helpful. Though there are already static optimization hints spread throughout the code (off the top of my head, MOZ_LIKELY/MOZ_UNLIKELY for marking conditionals).

[0] https://firefox-source-docs.mozilla.org/build/buildsystem/pg...

Re:Chrome just got faster with Profile Guided Optimization by loeg on Tuesday August 25, 2020 @02:20PM (#24274314)
Mozilla could publish their profile data for a given release image.
Re:Chrome just got faster with Profile Guided Optimization by glandium on Tuesday August 25, 2020 @07:36PM (#24277514)
They are public, but you have to know where to look. I do think they should be published alongside the builds on archive.mozilla.org. (disclaimer: I work for Mozilla)
Re:Chrome just got faster with Profile Guided Optimization by CalChris on Tuesday August 25, 2020 @04:34PM (#24275786)
Given PGO and branch prediction, has anyone tested whether turning off MOZ_LIKELY/MOZ_UNLIKELY makes any difference?