Re: Tuple and changes for m68k with -malign-int
Geert Uytterhoeven <[email protected]> Tue, 17 Jun 2025 09:40:45 +0200
| Newsgroups | gmane.linux.ports.m68k,gmane.linux.debian.ports.68k,gmane.comp.lib.glibc.user |
|---|---|
| Message-ID | <CAMuHMdV6zMWPOD_t0HoWgJDeGJardpqKgbZb9+HLCJZPsp-yCg@mail.gmail.com> |
Hi Adrian, On Tue, 17 Jun 2025 at 09:25, John Paul Adrian Glaubitz <[email protected]> wrote: > On Tue, 2025-06-17 at 09:02 +0200, Geert Uytterhoeven wrote: > > On Wed, 21 May 2025 at 04:15, John Klos <[email protected]> wrote: > > > Should Linux maintain a 32 bit platform that has alignment issues because > > > programmers make bad assumptions? > > > > Linux (the kernel) does maintain it, and bug fixes are backported > > to stable trees. The upstream kernel (outside the arch/m68k dir) > > has no problem fixing whatever alignment issues that pop up. > > This might change in the future when Rust code becomes more dominant in the kernel. > > What's going to happen when Rust code becomes mandatory in key parts of the kernel > and then we're unable to build it because we insisted on keeping the 2 byte ABI? We fix Rust? ;-) Is this a Rust issue, or an LLVM issue? In case of the latter, how does llvm-mos handle this? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds