https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96343
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> --- Thanks for the report. Yes, not sure we can reproduce it like this. We might need something smaller, more self-contained. In the meantime... Can you check if this still happens with trunk, or with GCC 10? If it doesn't, we don't have to chase a bug that has been solved already, and we can bisect to find the patch that fixed this (hopefully actually fixed, it might be just a side effect). Or, if it is still occurring, it is something we need to know as well :-)
