https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99581
--- Comment #12 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- (In reply to Vladimir Makarov from comment #11) > 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. Unfortunately, switching off the code results in 480 GCC test failures on aarhc64. I'll work on introducing new memory constraint. I hope to have a patch and submit it for review on Friday.