micky wrote:
In microsoft.public.windowsxp.general, on Thu, 14 Sep 2017 03:11:06
-0400, Paul wrote:


The browsers work in families. Chrome cut WinXP support and
32 bit support some time ago. Versions like SRWare Iron, they

What do they do about 32-bit win7 and win10?

OK, I'm mistaken. Here's the list.

https://en.wikipedia.org/wiki/Google_Chrome

"Chrome runs on:

* Windows 7 or later
* OS X 10.9 or later
* 64-bit versions of Ubuntu 14.04+, Debian 8+, openSUSE 13.1+ and Fedora 21+
* Android 4.1 or later
* iOS 9 or later

As of April 2016, stable 32-bit and 64-bit builds are available for Windows,
with only 64-bit stable builds available for Linux and macOS.

64-bit Windows builds became available in the developer channel and as
canary builds on June 3, 2014, in beta channel on July 30, 2014, and
in stable channel on August 26, 2014. 64-bit OS X builds became available
as canary builds on November 7, 2013, in beta channel on October 9, 2014,
and in stable channel on November 18, 2014.
"

So support for WinXP and Vista is gone, Windows7+ have x86 and x64.

Linux is x64 only. --- That's where the confusion came from. I assumed
consistency (like there was a reason for x64 only), but I guess not.
I still run 32-bit versions of Linux in virtual machines some times.

With several of the open source programs like Chromium, you need
an x64 OS to build an x86 executable. Some of these programs are
getting so big, the linking stage to build a DLL takes more than
3GB of RAM. You need a good sized machine to do it. Usually the
"build recipe" web pages warn about this. The people who build
Chrome at Google, were given CPUs with 20 cores, so they wouldn't
have to wait so long for builds to finish. That's how much of a
pig it is. I needed around a 45GB RAMdisk to hold everything
for a build (src and output), and there was only a little space
left when it finished (I was doing a debug build).

Paul