https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97205
--- Comment #21 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- Hi Srinath, when we add new assertions to gcc we use always a gcc_checking_assert nowadays, that is also the case here. The assertion is only firing in your compiler because it is a development snapshot 10.3.1. So that is an experimemtal version. That means the release version 10.3.0 will not have an ICE with this test case, except the long-standing potential wrong code due to unaligned memory access, however most contemporary ARM chips do no longer trap on an unaligned load/store. But on the other hand, this change might affects all targets whether or not they have any issue at all. So it might trigger a completely unrelated bug in a completely different area of the compiler. That said I do not object this back-port, I just wanted to say that it fixes a non-issue in a released compiler version. And even a small risk of a regression seems to be not worth it. Regards Bernd.
