Re: vldm on armhf?
Arnd Bergmann dixit: >gcc changed the way that you pass the floating point instruction set, >so instead of -march=armv7-a one should now pass -march=armv7-a+fp >to pick a target CPU that includes vfpv3-d16 FPU. But we pass neither! $ git grep -F armv7- | wc -l 0 >My guess is that in your case the compiler gets the wrong target CPU >and passes that down to the assembler, which then refuses to build >using FPU instructions. Hmm. So rebuild with -v on a porterbox? bye, //mirabilos -- you introduced a merge commit│ % g rebase -i HEAD^^ sorry, no idea and rebasing just fscked │ Segmentation should have cloned into a clean repo │ fault (core dumped) if I rebase that now, it's really ugh │ wuahh
Re: vldm on armhf?
Jeffrey Walton dixit: >If I recall correctly... Debian now uses ARMv7 for a default, which >enables NEON in the compiler. Automatically enabling NEON based on >ARMv7 is a GCC 11 change. Hmmh. But armhf used ARMv7 by default before, too, if I’m not mistaken. >(I thought Debian's armel went away recently). Nope, still very much active and listed as release architecture even. (And even if not, debian-ports do exist, and we want to support as many as possible.) I’m not an ARM programmer though. The port was done by multiple others and IIRC even slightly diverges from what upstream currently has, as we collected bugfixes in Debian which upstream ignored. So the specific details of which subarchitectures have which instructions are a bit beyond my paygrade (I do know about the differences between arm, armeb, armel, armhf-raspian, armhf-everyoneelse and arm64 though, just on a somewhat higher level). bye, //mirabilos -- >> Why don't you use JavaScript? I also don't like enabling JavaScript in > Because I use lynx as browser. +1 -- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel
Re: vldm on armhf?
On Wed, Jul 20, 2022 at 3:40 PM Thorsten Glaser wrote: > > Dixi quod… > > >did something change wrt. compiler defaults on armhf recently? > > armel also FTBFS with SIGILL in the testsuite. > > So something changed incompatibly between 2019-11-10 and now > in the ARM toolchain. But what, and how can I get this to work > again? If I recall correctly... Debian now uses ARMv7 for a default, which enables NEON in the compiler. Automatically enabling NEON based on ARMv7 is a GCC 11 change. (I thought Debian's armel went away recently). Also see GCC Bug 104455, https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104455 . Jeff
Re: vldm on armhf?
On Wed, Jul 20, 2022 at 9:35 PM Thorsten Glaser wrote: > > Dixi quod… > > >did something change wrt. compiler defaults on armhf recently? > > armel also FTBFS with SIGILL in the testsuite. > > So something changed incompatibly between 2019-11-10 and now > in the ARM toolchain. But what, and how can I get this to work > again? gcc changed the way that you pass the floating point instruction set, so instead of -march=armv7-a one should now pass -march=armv7-a+fp to pick a target CPU that includes vfpv3-d16 FPU. My guess is that in your case the compiler gets the wrong target CPU and passes that down to the assembler, which then refuses to build using FPU instructions. Arnd
Re: vldm on armhf?
Dixi quod… >did something change wrt. compiler defaults on armhf recently? armel also FTBFS with SIGILL in the testsuite. So something changed incompatibly between 2019-11-10 and now in the ARM toolchain. But what, and how can I get this to work again? Thanks in advance, //mirabilos -- Solange man keine schmutzigen Tricks macht, und ich meine *wirklich* schmutzige Tricks, wie bei einer doppelt verketteten Liste beide Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
