-
Notifications
You must be signed in to change notification settings - Fork 15.3k
AMDGPU: Avoid report_fatal_error for reporting libcalls #145134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMDGPU: Avoid report_fatal_error for reporting libcalls #145134
Conversation
|
@llvm/pr-subscribers-backend-amdgpu Author: Matt Arsenault (arsenm) ChangesFull diff: https://github.com/llvm/llvm-project/pull/145134.diff 1 Files Affected:
diff --git a/llvm/lib/Target/AMDGPU/SIISelLowering.cpp b/llvm/lib/Target/AMDGPU/SIISelLowering.cpp
index 07d79d677104a..b752ccd6e14b1 100644
--- a/llvm/lib/Target/AMDGPU/SIISelLowering.cpp
+++ b/llvm/lib/Target/AMDGPU/SIISelLowering.cpp
@@ -3805,7 +3805,7 @@ SDValue SITargetLowering::LowerCall(CallLoweringInfo &CLI,
}
if (!CLI.CB)
- report_fatal_error("unsupported libcall legalization");
+ return lowerUnhandledCall(CLI, InVals, "unsupported libcall legalization");
if (IsTailCall && MF.getTarget().Options.GuaranteedTailCallOpt) {
return lowerUnhandledCall(CLI, InVals,
|
|
Then how the error will look now for an user? |
Should be |
|
but there is no test for that? |
Ideally we should have one... But there was not one before too. |
This isn't really supposed to happen in the first place so there isn't a reliable test. Would need to have a known broken operation |
|
but if that should really not happen, existing |
report_fatal_error is never good. Also it's highly likely to appear with the legalizer's bias towards libcalls by default |

No description provided.