https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81101

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
End-users aren't meant to see this; this is for people building GCC from
source, with checking enabled (the self-tests are a no-op in a release build).

So the "user" in question here is a developer, packager, or (very) early
adopter.

We want a backtrace when a selftest fails, and for it to abort the process.

Would "selftest failure" rather than "internal compiler error" be better?  (and
maybe leave out the bug report thing?)

Or were you wanting some kind of additional descriptive text in the failure
message?

Reply via email to