Nuno Lopes 80b3dcc045 [Support] Make report_fatal_error respect its GenCrashDiag argument so it doesn't generate a backtrace
There are a few places where we use report_fatal_error when the input is broken.
Currently, this function always crashes LLVM with an abort signal, which
then triggers the backtrace printing code.
I think this is excessive, as wrong input shouldn't give a link to
LLVM's github issue URL and tell users to file a bug report.
We shouldn't print a stack trace either.

This patch changes report_fatal_error so it uses exit() rather than
abort() when its argument GenCrashDiag=false.

Reviewed by: nikic, MaskRay, RKSimon

Differential Revision: https://reviews.llvm.org/D126550
2022-05-30 19:19:23 +01:00
..
2019-05-15 12:41:58 +00:00
2021-07-07 10:21:07 +01:00
2021-07-01 21:08:13 +01:00
2020-06-18 17:26:24 +01:00
2020-12-08 11:54:39 +00:00
2019-10-08 08:25:42 +00:00
2020-04-09 10:36:00 +01:00
2021-03-17 15:29:02 +00:00
2019-02-26 12:02:12 +00:00
2019-12-12 13:51:39 +00:00
2019-06-11 11:09:25 +00:00
2021-11-21 18:33:29 +00:00
2020-01-21 10:40:17 +00:00
2019-07-27 18:44:15 +00:00
2020-12-08 11:54:39 +00:00
2020-07-16 11:25:53 +01:00
2019-10-08 08:25:42 +00:00
2020-10-07 11:47:03 +01:00
2020-12-08 11:54:39 +00:00
2019-11-04 13:37:01 +00:00
2019-10-08 08:25:42 +00:00