583628 - Do 32-bit Windows builds on 64-bit Windows

Status: RESOLVED DUPLICATE of bug 709480

(Infrastructure & Operations Graveyard :: CIDuty, task, P5)

Description

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

https://bugzilla.mozilla.org/show_bug.cgi?id=582335#c52

Should be tested of course.

Comment 1

[(not currently active) Ted Mielczarek]

FWIW, plenty of developers build in this configuration (myself included). I suspect the main reason being that we all want 4+ GB of ram, and using that requires using a 64-bit Windows.

Comment 2

[Chris Cooper [:coop] (he/him)]

How much pressure are we currently feeling to make this change now that bug 582335 is fixed? 

jhford will be tackling the linux-equivalent of this soon (bug 633275).

Comment 3

[(not currently active) Ted Mielczarek]

It's less critical, but I have no doubt that we will creep our way back up in codesize to the point where we'll hit this again. This would buy us a whole extra gig of virtual memory, which is a lot of breathing room. Possibly enough to see us through to a world where we can either compile a 32-bit binary with a 64-bit compiler, or drop support for 32-bit builds.

Comment 4

[(not currently active) Ted Mielczarek]

For reference, here's our linker VM usage from a recent Win PGO build:
linker max virtual size: 2970206208 (bytes)

If that hits 3GB, we're toast.

Comment 5

[Phil Ringnalda (:philor)]

It's tough to choose one of the two bugs, but I think (looking at a build that just died for lack of virtual memory, wondering whether or not a retrigger will also hit it) that edmorley came closer to the way we'll actually fix this, as a P1 blocker rather than a P5 enhancement.