https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> --- Can we (did we already?) fix the diagnostic with respect to the range printing as said in comment#5? I'd defer the rest. Maybe we can even have jump-threading cancel paths that would introduce these kind of stmts? But folding them to __builtin_trap() looks a legitimate way to deal with them, the region RPO VN code could be thrown at jump-threaded paths and do this immediately.
