On Tue, 2024-08-06 at 16:21 +0200, Arnd Bergmann wrote: > I believe the builds are all done on arm64 hardware, and the table > lists the same issue for available hardware on armel, armhf and arm64. > > There are a few instructions that armel binaries can use that > are missing on armv8 hardware (cp15 barriers, swp/swpb atomics), > and a few differences in how the kernel treats unaligned memory > access and personality. Emulation for these is a bit tricky to > set up correctly for individual developers, but but the > build servers should generall just work.
Thanks for the clarification. > Most of issues with armel packages are about libatomic link > time requirements, and about applications that hardcode armv7 > or vfp instruction extensions. Code that hardwires CPU baselines is considered RC-buggy anyway, so that shouldn't be an argument. And that notoric libatomic issue is just something that should be finally fixed in GCC upstream (unless I am missing something why that can't be done). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
