https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99581
--- Comment #11 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- Introducing a new memory constraint can take some time. I guess we could switch off the offending code meanwhile because it is compiler crash vs unoptimal generated code choice. I'll investigate how switching the code off affects GCC tests on aarhc64.