[cfarm-users] What are people testing 32-bit builds on?

Jonathan Wakely jwakely.gcc at gmail.com
Thu May 14 20:12:33 CEST 2026


On Thu, 14 May 2026 at 17:51, Peter Gutmann via cfarm-users
<cfarm-users at lists.tetaneutral.net> wrote:
>
> This is more of a general question to the studio audience, but with cfarm26/26
> being the last 32-bit machines (AFAIK) what are people using to test 32-bit
> builds on?  I've been looking at possible Y2038 implications now that it's
> getting closer, with Linux (so cfarm26/27) the problem is sidestepped due to
> the use of a 64-bit time_t

By default time_t is still 32-bit on i686 Linux, although recent
versions of Glibc have a macro to enable 64-bit time_t, and the kernel
uses a 64-bit type internally.

> but for other 32-bit OSes it presumably won't be.
> What are people testing 32-bit non-Linux+x86 builds on?

g++ -m32

> I've got some older
> SBCs (MIPS, Arm) running old versions of Linux that I keep around, but is
> there anything still sold that's 32-bit Arm (preferably anything but a Pi)
> that I can drop one or more of the BSDs on for testing without spending a ton
> of time making it work?  It used to be that you had to go out of your way to
> find aarch64 systems to test on, now it's the other way round...

Compilers on Solaris default to generating 32-bit code.

Can't you run an x86 VM on an x86_64 host?


More information about the cfarm-users mailing list