-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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: Support llvm.exp10 #65860
AMDGPU: Support llvm.exp10 #65860
Conversation
d54d7b7
to
dcb3d6e
Compare
ping |
✅ With the latest revision this PR passed the C/C++ code formatter. |
ping |
1 similar comment
ping |
ping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot verify whether that approximation is reasonable, but aside from my one comment it looks good.
@@ -349,10 +350,10 @@ AMDGPUTargetLowering::AMDGPUTargetLowering(const TargetMachine &TM, | |||
setOperationAction(ISD::IS_FPCLASS, {MVT::f16, MVT::f32, MVT::f64}, Legal); | |||
else { | |||
setOperationAction(ISD::IS_FPCLASS, {MVT::f32, MVT::f64}, Legal); | |||
setOperationAction({ISD::FLOG2, ISD::FEXP2}, MVT::f16, Custom); | |||
setOperationAction({ISD::FLOG2, ISD::FEXP2, ISD::FEXP10}, MVT::f16, Custom); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like setting FEXP10 for f16 Custom here is redundant with the line below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, do we need to add the approximate lowering to GlobalISel as well at some point?
- run clang-format as well, formatter checks failed
I'm ignoring it since it mangles action builder calls badly |
Both should be implementing the same thing as-is? |
No description provided.