Re: Tuple and changes for m68k with -malign-int
John Paul Adrian Glaubitz <[email protected]> Tue, 17 Jun 2025 13:37:45 +0200
| Newsgroups | gmane.linux.ports.m68k,gmane.linux.debian.ports.68k,gmane.comp.lib.glibc.user |
|---|---|
| Message-ID | <f0f2fe26ef68647025b5f5d99136867b11a752bc.camel@physik.fu-berlin.de> |
On Tue, 2025-06-17 at 13:21 +0200, Geert Uytterhoeven wrote: > > I'm not sure how this is relevant at all. What is the gross profit of the NetBSD organization? > > IOW, you can have plenty of ABIs, if you have the manpower to create > and maintain them. Both Debian and Gentoo want to maintain the 4 bytes alignment ABI in the long term. I don't think there is a point to continue to maintain the 2 bytes alignment ABI. For whom would we do that? > > > > > Is this a Rust issue, or an LLVM issue? > > > > > > > > https://github.com/M680x0/M680x0-mono-repo/issues/10 > > > > > > So you mean it's an LLVM issue. > > > > It's an issue on many projects that use things like tagged pointers etc. > > I know. If you want to tag pointers, it is your responsibility to use > unused bits (Hi Apple 24-bit). When using the low bit(s) for tagging, > you have to make sure the objects you are pointing to are sufficiently > aligned. BTW, how does LLVM tag pointers to chars? I don't know. I'm not an expert on the LLVM codebase even though I made some contributions. If you know how to address this issue I'm curious to hear about the fix. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913