Hi,

I just noticed the following in latest changelog:

Split more targets from chrome.gyp to add support for building Native Client for 64bit Windows. This CL is required for supporting Native Client on 64bit Windows. On Win64 we will use a 64bit executable to load NaCl modules. Since we have only one version of Chrome on Windows, this executable has to be built together with 32bit Chrome binaries. For the targets that are required for both 32bit and 64bit builds, this CL moves the shared parts of the target definitions into targetspecific gypi files (such as base.gypi). New 64bit only targets are added. Since we would like to port as few code as possible at this point, some 64bit targets include less source files or less dependencies than the original 32bit targets. These targets will have nacl_win64 in their name to emphasize that they should be used for NaCl only. Some 64bit targets are identical to the 32bit targets in everything except for the target platform these will have only win64 in their name.

So seems as we'r going to have a nice 64 bit client in the near future :=)
Those that runs/ran firefox x64 will know the pros and cons..
The speed of the FF version is amasing, so if possible, it will make Chrome even faster.. The downside is of cause that not eveything has been ported to x64 yet, flash for instance is still stucked in the past and will not work :=)

Currently, there are in-development testing builds of 64-bit Linux Chromium at:

http://build.chromium.org/buildbot/s...ux-64/?C=M;O=D

Other 64-bit Chrome issues you may be interested in:

http://crbug.com/8606 - 64 bit chrome on Windows
http://crbug.com/18323 - Need more bits (64-bit Mac version)
http://crbug.com/27218 - Port the windows chromium sandbox to 64 bits

And all the others:

http://code.google.com/p/chromium/is...2&q=summary:64