https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99694
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Richard Biener from comment #14) > I disagree - syntactically valid input should not crash the compiler or make > it slow. Yes, fixing cases with obvious non-sensical input might be low > priority, but the exposed issues are often also issues for "correct" > programs. Yeah. I don't think ICEs/compiler hangs etc. on syntactically valid programs with UB somewhere in it should be low priority, UB happens at runtime when some statement is encountered and perhaps certain conditions are met, but there is no guarantee those conditions will be met in the testcase at runtime or the statement will be encountered. Then there are ICEs/compiler hangs etc. on syntactically invalid programs, if it happens without reporting errors the priority isn't much lower, if it happens after reporting errors it is much lower priority (error recovery bugs). Of course, for programs that invoke UB at runtime, anything that happens during the runtime after encountering the UB is a non-bug.
