https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93384
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Perhaps a workaround (and probably the right thing in any case) would be to add _Py_NO_RETURN to _PyObject_AssertFailed declaration in Include/cpython/object.h because it will always call Py_FatalError which is already _Py_NO_RETURN marked.
