llvm-project/llvm/test/CodeGen/Lanai
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
..
codemodel.ll [Support] Make report_fatal_error respect its GenCrashDiag argument so it doesn't generate a backtrace 2022-05-30 19:19:23 +01:00
comparisons_i32.ll
comparisons_i64.ll
constant_multiply.ll
delay_filler.ll
i32.ll
inlineasm-output-template.ll
lanai-misched-trivial-disjoint.ll
lit.local.cfg
lowering-128.ll [Lanai] implement wide immediate support 2021-09-10 10:54:43 +00:00
lshift64.ll
masking_setccs.ll
mem_alu_combiner.ll
multiply.ll
peephole-compare.mir
rshift64.ll
select.ll
set_and_hi.ll
shift.ll
stack-frame.ll
sub-cmp-peephole.ll
subword.ll