Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:LibXUL on Win32 approaching 4GB memory limit (Score 5, Informative) 127

by HoserHead (#43735359) Attached to: How Maintainable Is the Firefox Codebase?

I'm a Firefox developer.

This is slightly inaccurate. We aren't running out of memory to link Firefox, we're running out of memory to run Profile-Guided Optimization (PGO) on Firefox.

PGO looks at what is actually executed during a given workload and optimizes based on that. It can be a pretty big win — 30% in some workloads —so we work pretty hard to keep it going.

Unfortunately, PGO needs to have not only all the code, but all the intermediate representations and other metadata about the code in memory at one time. (That's why we're running out of memory.)

Unfortunately, MSVC doesn't support producing a 32-bit binary using their 64-bit compiler.

(FWIW, Chrome has *always* been too big to use PGO.)

MOUNT TAPE U1439 ON B3, NO RING

Working...