Re: Tuple and changes for m68k with -malign-int
Geert Uytterhoeven <[email protected]>
| Newsgroups | gmane.comp.lib.glibc.user,gmane.linux.debian.ports.68k,gmane.linux.ports.m68k |
|---|---|
| Message-ID | <CAMuHMdUV0oM=zp6dG0KNbPJz2m7KBhynHa=ENUJmfh=u3gisbg@mail.gmail.com> |
On Sun, Aug 27, 2023 at 11:36 AM James Le Cuirot <chewi-Yn+4UywRBy5n8C+U7lyxXlpr/1R2p/[email protected]> wrote: > On Sun, 2023-08-27 at 10:46 +1000, Finn Thain wrote: > > Moreover, why is it that only a few developers have a problem with making > > explicit their decisions regarding alignment of shorts? What actual pain > > does it cause them to accept a patch to make their struct layouts plain? > > Some projects do accept patches. Yann Collet was even kind enough to fix this > in zstd themselves. On the other hand, we have had to fight to stop Python > from dropping m68k support entirely. The real problem is the effort required > to produce these patches. I haven't been able to wrap my head around this so > far, but I would still like to learn. I could see myself eventually fixing > mold, but LLVM feels like a very tall order. Perhaps we need a new compiler warning: "hole in structure due to non-natural alignment, please consider adding explicit padding"? 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