https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109237
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- There's similar issues with GIMPLE uses of last_stmt () which generally (but not always) want to look at a possible control transfer stmt. It looks like we're not guaranteed to have no debug stmts after such, in particular CFG cleanup seems to be ready to remove debug stmts after a noreturn call. But GIMPLE verify_flow_info should already choke on that, so it might be only a temporary thing to accept?
