Results 1 to 5 of 5

Thread: 32 bit 'end of life's coming. Developers can't build firefox any longer on 32bit.

  1. #1
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default 32 bit 'end of life's coming. Developers can't build firefox any longer on 32bit.

    the Developers hit the address space limit for a PGO-build

    English news:
    http://www.h-online.com/open/news/it...s-1393772.html

    German news:
    http://www.heise.de/open/meldung/Fir...n-1393652.html

  2. #2
    Join Date
    Dec 2011
    Posts
    54

    Default They should know their limits.

    Address space limit? I'm about to reach my ram limit just running this browser.

    One day it'll take 10 google-bytes(amount of memory to fit whole search engine) of ram to build Firefox. Developers will have to claim Antarctica. This should be adequate for building a super computer, that's hopefully powerful enough to compile Firefox.

  3. #3
    Join Date
    Apr 2010
    Posts
    1,946

    Default

    What are you talking about, I build my Fx every version on Gentoo box. Its x64 though, no way I try this or LibreOffice on x86-32.
    Can anyone suggest them they use PAE kernel just for building? Should work.

  4. #4
    Join Date
    Sep 2007
    Location
    Connecticut,USA
    Posts
    974

    Default

    Quote Originally Posted by crazycheese View Post
    What are you talking about, I build my Fx every version on Gentoo box. Its x64 though, no way I try this or LibreOffice on x86-32.
    Can anyone suggest them they use PAE kernel just for building? Should work.
    Or maybe build the 32 bit Windows version using gcc on linux instead

    Now why should a linker need more than 3GB of RAM to build the executable files? Perhaps experts on linkers/loaders can shed some light on the issue

  5. #5

    Default

    Sounds like they're doing profile-guided link time optimization. That means the linker looks at the whole source code (or some intermediate representation), and the gathered usage profiles that tell it how to optimize it. The more source you have, the more ram you need to look at all of it (and possibly they include some libraries as well in that).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •