Re: compile and run 32bit programs on aarch64eb

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Mon, Dec 08, 2025 at 20:07:44 +1100, matthew green wrote:

> Martin Husemann writes:
> > On Wed, Nov 26, 2025 at 04:26:30PM +0300, Valery Ushakov wrote:
> > > sligtly different set of atomic primitives is provided by the compat
> > > libc (this might or might not be a bug, I couldn't get an answer from
> > > people in the know).
> >
> > I think this is because on sparc64 we know the hardware is at least sun4u,
> > so we can assume all sparcv9 instructions are available, while the regular
> > sparc libs are build for sparcv7 (with optional overlays for sparcv8).
>
> yes - this is on purpose, and designed to run 32-bit on v9 CPU.

[Apologies for sparc spam on arm list, but I don't want to tear the
thread.]

Is it intended to support:

1) Code compiled on sparc64 with -m32?  E.g. I use this to compile and
run sparc versions of Inferno and Self (that don't support 64-bit) on
a much faster sparc64 machine.

2) Code compiled on sparc natively?  I.e. pre-existing sparc binaries
that come from sparc and now you want to run them on sparc64.  See the
case of sparc gdb binary missing some functions I mentioned upthread.

3) Both?

4) Apropos... IIRC, native sparc64 gdb cannot debug sparc64 -m32
binaries, hence the sparc gdb on sparc64 scenario above.  (But it's
been a while and that noisy ultra is turned off at the moment, so I
cannot check, sorry).


-uwe