On 2013-02-04 10:07 PM, Ryan VanderMeulen wrote:
On 2/4/2013 9:59 PM, Dave Mandelin wrote:
I was talking to Taras and Naveed about this today, and what also came
up was:
4. Do the work to make 64-bit JS jit perf as good as 32-bit JS jit
perf, and then switch to x64 builds for Windows. There are of course
many issues involved with such a switch, but I believe that would fix
the linker memory limit problem, and "make x64 jit perf real good"
seems much more useful and rewarding long-term than trying to patch up
a 32-bit build process that MS may not even be that interested in
supporting any more.
Dave
Except that MSVC uses the 32bit linker for 64bit builds too (as was said
earlier in this thread). Not sure if that's the case for MSVC 2012, though.
That's not correct, MSVC has a 64-bit linker which can generate x86-64
code. The problem with that is that it seems a lot buggier than the
32-bit linker which generates x86 code, to the point that currently we
cannot do 64-bit PGO builds because of an internal compiler error on
mozilla-central.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
