Advise to call 'internal_error' instead of 'abort' or 'fancy_abort'

gcc/
	* diagnostic.cc: Don't advise to call 'abort' instead of
	'internal_error'.
	* system.h: Advise to call 'internal_error' instead of 'abort' or
	'fancy_abort'.

Suggested-by: Richard Biener <richard.guenther@gmail.com>
This commit is contained in:
Thomas Schwinge
2022-05-10 15:56:08 +02:00
parent 0f00ebf0d6
commit cd4a0ddc12
2 changed files with 5 additions and 5 deletions

View File

@@ -1935,9 +1935,7 @@ fatal_error (location_t loc, const char *gmsgid, ...)
}
/* An internal consistency check has failed. We make no attempt to
continue. Note that unless there is debugging value to be had from
a more specific message, or some other good reason, you should use
abort () instead of calling this function directly. */
continue. */
void
internal_error (const char *gmsgid, ...)
{

View File

@@ -774,8 +774,10 @@ extern int vsnprintf (char *, size_t, const char *, va_list);
#endif
#endif
/* Redefine abort to report an internal error w/o coredump, and
reporting the location of the error in the source file. */
/* Redefine 'abort' to report an internal error w/o coredump, and
reporting the location of the error in the source file.
Instead of directly calling 'abort' or 'fancy_abort', GCC code
should normally call 'internal_error' with a specific message. */
extern void fancy_abort (const char *, int, const char *)
ATTRIBUTE_NORETURN ATTRIBUTE_COLD;
#define abort() fancy_abort (__FILE__, __LINE__, __FUNCTION__)