From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: James Le Cuirot <chewi@aura-online.co.uk>
Cc: libc-help@sourceware.org,
debian-68k <debian-68k@lists.debian.org>,
linux-m68k <linux-m68k@vger.kernel.org>
Subject: Python requires 32-bit alignment now - was: Re: Tuple and changes for m68k with -malign-int
Date: Wed, 15 May 2024 19:08:47 +0200 [thread overview]
Message-ID: <6009464ec0602cbf9e0262d955020438beeda18a.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <10cbcb8a65639f88e7eeb503fd02df172bc46a07.camel@physik.fu-berlin.de>
Hi,
On Sat, 2023-08-26 at 12:51 +0200, John Paul Adrian Glaubitz wrote:
> > The Debian m68k maintainers proposed building their packages with -malign-int
> > last year, aligning to 32-bit instead of 16-bit, which improves compatibility
> > with some projects and should give better performance on 68020+, at the cost
> > of slightly increased memory usage. The mold linker is at least one project
> > that has been shown to work after making this change where it previously
> > didn't.
>
> Not only mold but also most notably the following projects:
>
> - LLVM
> - Firebird Database
> - OpenJDK
> - Various Qt packages
We can now add CPython to this list as 3.13 requires 32-bit alignment [1]:
In file included from ../Include/internal/pycore_backoff.h:12,
from ../Include/internal/pycore_code.h:474,
from ../Include/internal/pycore_interp.h:16,
from ../Include/internal/pycore_runtime.h:17,
from ../Include/internal/pycore_pystate.h:12,
from ../Include/internal/pycore_critical_section.h:9,
from ../Python/critical_section.c:4:
../Python/critical_section.c:6:1: error: static assertion failed: "critical section must be aligned to at least 4 bytes"
6 | static_assert(_Alignof(_PyCriticalSection) >= 4,
| ^~~~~~~~~~~~~
We should really make the switch now. It's certainly not getting better.
Adrian
> [1] https://buildd.debian.org/status/fetch.php?pkg=python3.13&arch=m68k&ver=3.13.0%7Eb1-2&stamp=1715773703&raw=0
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2024-05-15 17:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 8:53 James Le Cuirot
2023-08-26 10:51 ` John Paul Adrian Glaubitz
2023-08-26 19:24 ` Richard
2023-08-26 20:43 ` James Le Cuirot
2023-08-28 6:54 ` Geert Uytterhoeven
2023-08-28 10:57 ` John Paul Adrian Glaubitz
2023-08-28 12:11 ` Richard
2023-08-28 12:22 ` Geert Uytterhoeven
2023-08-28 12:46 ` John Paul Adrian Glaubitz
2023-08-27 0:46 ` Finn Thain
2023-08-27 9:20 ` James Le Cuirot
2023-08-27 11:27 ` Richard
2023-08-28 7:00 ` Geert Uytterhoeven
2023-08-28 11:26 ` Richard
2023-08-28 11:40 ` Geert Uytterhoeven
2023-08-28 20:16 ` Richard
2023-08-29 6:52 ` Geert Uytterhoeven
2023-08-28 6:56 ` Geert Uytterhoeven
2023-08-28 11:13 ` John Paul Adrian Glaubitz
2023-08-29 1:12 ` Finn Thain
2023-08-28 11:10 ` John Paul Adrian Glaubitz
2023-08-28 12:44 ` Adhemerval Zanella Netto
2023-08-28 12:50 ` John Paul Adrian Glaubitz
2023-08-28 13:17 ` Andreas Schwab
2023-08-29 10:51 ` John Paul Adrian Glaubitz
2023-08-29 15:27 ` Geert Uytterhoeven
2023-08-28 13:29 ` James Le Cuirot
2023-08-29 10:54 ` John Paul Adrian Glaubitz
2023-08-29 21:53 ` Karoly Balogh
2023-08-30 1:33 ` Jeffrey Walton
2023-08-29 1:14 ` Finn Thain
2023-08-29 8:52 ` Eero Tamminen
2024-05-15 17:08 ` John Paul Adrian Glaubitz [this message]
2023-08-28 5:15 ` Florian Weimer
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=6009464ec0602cbf9e0262d955020438beeda18a.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=chewi@aura-online.co.uk \
--cc=debian-68k@lists.debian.org \
--cc=libc-help@sourceware.org \
--cc=linux-m68k@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).