From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 68202@debbugs.gnu.org
Subject: [bug#68202] [PATCH 0/5] Add support for x86_64-linux-gnux32
Date: Mon, 08 Jan 2024 18:14:07 +0100 [thread overview]
Message-ID: <875y034ujk.fsf@gnu.org> (raw)
In-Reply-To: <cover.1704179455.git.efraim@flashner.co.il> (Efraim Flashner's message of "Tue, 2 Jan 2024 09:26:13 +0200")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
> I was reminded recently about a comment I made back in February 2017
> about getting guix support for x32, aka x86_64-linux-gnux32, aka
> x86_64-linux but with 32-bit data structures. The idea was that by
> using 32-bit pointers there'd be a not insignificant speed-up of code
> execution¹. I am uncertain how true this is, or which packages would
> really benefit from this.
Interesting!
I’m not sure why this target hasn’t been picked up by ci.guix. (gnu ci)
calls ‘targets’, which returns it. Weird.
> ¹ https://en.wikipedia.org/wiki/X32_ABI
It’s not clear how long support for this ABI will live on in the
toolchain…
Cheers,
Ludo’.
prev parent reply other threads:[~2024-01-08 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 7:26 [bug#68202] [PATCH 0/5] Add support for x86_64-linux-gnux32 Efraim Flashner
2024-01-02 7:27 ` [bug#68202] [PATCH 1/5] gnu: " Efraim Flashner
2024-01-02 7:27 ` [bug#68202] [PATCH 2/5] gnu: Add target-x32? Efraim Flashner
2024-01-08 9:20 ` Simon Tournier
2024-01-08 10:05 ` Efraim Flashner
2024-01-02 7:27 ` [bug#68202] [PATCH 3/5] gnu: openssl: Fix building on x86_64-linux-gnux32 Efraim Flashner
2024-01-02 7:27 ` [bug#68202] [PATCH 4/5] gnu: gmp: " Efraim Flashner
2024-01-02 7:27 ` [bug#68202] [PATCH 5/5] gnu: libsigsegv: Fix building for x86_64-linux-gnux32 Efraim Flashner
2024-01-03 8:43 ` Mathieu Othacehe
2024-01-03 8:53 ` Efraim Flashner
2024-01-05 11:22 ` bug#68202: [PATCH 0/5] Add support " Efraim Flashner
2024-01-08 17:14 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y034ujk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=68202@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).