https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124126
Alice Carlotti <acarlotti at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acarlotti at gcc dot gnu.org
--- Comment #9 from Alice Carlotti <acarlotti at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> I don't know why it started to fail now though.
Prior to r15-3025-gfceecc511d4918 (which was backported to gcc-14 but no
further), the ls64 intrinsics and type were gated by the target features at
initialisation time. This meant that if `+ls64` isn't enabled, then the
initialisation code didn't run and the bug in this PR wouldn't arise.
After that point, the intrinsics and type are unconditionally available, with
time-of-use feature checks for using the intrinsics.
I've not verified this, but adding `+ls64`` to the command line architecture
options should make this fail on every branch back to gcc 12 (when these
intrinsics were first added).