https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102472
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- On the GCC 11 branch head I cannot reproduce this with a x86_64-linux -> m68k-linux cross cc1, using -O2 -fwrapv -fPIC -g2 -Wno-unused-result -Wsign-compare -Wall Can you clarify that it is the compiler that enters an infinite loop rather than the object being miscompiled and python-uvloop entering an infinite loop? Can you also please quote the output of the compiler-command when you add -v to the command-line that causes the hang? In particular the line showing the cc1 execution is useful. Note I did not test GCC 11.2.0 exactly.
