From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Arnd Bergmann <arnd@arndb.de>,
Richard Henderson <richard.henderson@linaro.org>,
Matt Turner <mattst88@gmail.com>, Kees Cook <kees@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-alpha@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Michael Cree <mcree@orcon.net.nz>,
Sam James <sam@gentoo.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
Chris Hofstaedtler <zeha@debian.org>,
util-linux@vger.kernel.org, linux-mips@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH] alpha: Fix personality flag propagation across an exec
Date: Thu, 9 Jan 2025 20:10:39 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.21.2501091953050.18889@angie.orcam.me.uk> (raw)
In-Reply-To: <87ed1cufj1.fsf@email.froward.int.ebiederm.org>
On Thu, 9 Jan 2025, Eric W. Biederman wrote:
> > So, this would be the 100% correct for alpha then which would not loose
> > any functionality even for 32-bit binaries?
>
> I don't think it is correct to think about 32-bit binaries on alpha.
>
> Alpha never had a 32bit instruction set. But at some point it looks
> like binaries that could not handle more than 31 bits of address
> space got ported and someone implemented a work-around. I guess this
> is the --taso option that Arnd mentioned.
This also saves some code space in non-PIE and plain static executables
as it takes fewer machine instructions to load a 64-bit address that is
known beforehand to be a sign-extended 32-bit value.
This is similar to the MIPS n32 ABI, which also implies a 32-bit address
space while still using 64-bit registers for everything, starting from
stack slots (it's also ILP32 with the `long long' C data type only making
proper use of the full width of the CPU registers, while Alpha's --taso
ABI is I believe IP32 (?) with the plain `long' C data type still 64-bit,
just as with the regular LP64 ABI).
This saving turned out quite important for some MIPS applications; less
so for the Alpha, where indeed it was mainly a portability matter at the
time when going beyond 32 bits (and writing clean code in the first place)
was a big thing for some people.
Maciej
next prev parent reply other threads:[~2025-01-09 20:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 14:01 John Paul Adrian Glaubitz
2025-01-08 22:49 ` Kees Cook
2025-01-09 0:52 ` Jeff Xu
2025-01-09 8:01 ` Arnd Bergmann
2025-01-09 8:43 ` Arnd Bergmann
2025-01-09 8:46 ` John Paul Adrian Glaubitz
2025-01-09 8:56 ` Arnd Bergmann
2025-01-09 9:12 ` John Paul Adrian Glaubitz
2025-01-09 16:18 ` Eric W. Biederman
2025-01-09 16:52 ` Arnd Bergmann
2025-01-09 17:17 ` Eric W. Biederman
2025-01-09 20:10 ` Maciej W. Rozycki [this message]
2025-01-09 20:53 ` Arnd Bergmann
2025-01-12 14:40 ` Maciej W. Rozycki
2025-01-10 0:28 ` Richard Henderson
2025-01-11 0:16 ` [PATCH] alpha/elf: Fix misc/setarch test of util-linux by removing 32bit support Eric W. Biederman
2025-01-11 1:17 ` Richard Henderson
2025-01-11 10:37 ` John Paul Adrian Glaubitz
2025-01-12 14:40 ` Maciej W. Rozycki
2025-01-12 14:56 ` John Paul Adrian Glaubitz
2025-01-13 5:39 ` [PATCH v2] " Eric W. Biederman
2025-01-18 10:35 ` Ivan Kokshaysky
2025-01-26 17:15 ` John Paul Adrian Glaubitz
2025-01-27 13:27 ` Ivan Kokshaysky
2025-02-03 11:55 ` John Paul Adrian Glaubitz
2025-02-06 15:42 ` Kees Cook
2025-01-11 11:26 ` [PATCH] " Arnd Bergmann
2025-01-11 15:27 ` Ivan Kokshaysky
2025-01-13 5:32 ` Eric W. Biederman
2025-01-11 21:26 ` John Paul Adrian Glaubitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2501091953050.18889@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kees@kernel.org \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=loongarch@lists.linux.dev \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=paulmck@kernel.org \
--cc=richard.henderson@linaro.org \
--cc=sam@gentoo.org \
--cc=util-linux@vger.kernel.org \
--cc=zeha@debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox