aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/ProgramStack.cpp
diff options
context:
space:
mode:
authorPaul Bowen-Huggett <paulhuggett@mac.com>2025-04-15 17:52:00 +0200
committerGitHub <noreply@github.com>2025-04-15 08:52:00 -0700
commit7b5a459611212b650e863c0ad6a9fa49c07e29df (patch)
tree55eb0333c1f5e24509135bef129b8f97df11b593 /llvm/lib/Support/ProgramStack.cpp
parent88b6229dc3f65876b3f627616a024cd5dbcadcb0 (diff)
downloadllvm-7b5a459611212b650e863c0ad6a9fa49c07e29df.zip
llvm-7b5a459611212b650e863c0ad6a9fa49c07e29df.tar.gz
llvm-7b5a459611212b650e863c0ad6a9fa49c07e29df.tar.bz2
[RISCV] Just reporting an error shouldn't generate a crash diagnostic (#134040)
Wanting to examine some of generated code, I tried MCA with the command: ~~~bash llvm-mca -mtriple=riscv32-unknown-unknown -mcpu=rocket -iterations=300 core_list_join.s ~~~ I was greeted with the following error message: ~~~ LLVM ERROR: RV32 target requires an RV32 CPU PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace. Stack dump: … ~~~ On beginning to investigate the “bug”, I discovered that the code was simply attempting to report a user error. It used report_fatal_error() to do so but with the “bool GenCrashDiag” argument enabled (the default). This tiny change adds a wrapper function which calls report_fatal_error() as before but with GenCrashDiag disabled.
Diffstat (limited to 'llvm/lib/Support/ProgramStack.cpp')
0 files changed, 0 insertions, 0 deletions