Skip to content

[NFC] Update isVectorIntrinsicWith... functions to consider TargetTransformInfo #117030

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

Closed
3 tasks
inbelic opened this issue Nov 20, 2024 · 0 comments · Fixed by #117635
Closed
3 tasks

[NFC] Update isVectorIntrinsicWith... functions to consider TargetTransformInfo #117030

inbelic opened this issue Nov 20, 2024 · 0 comments · Fixed by #117635

Comments

@inbelic
Copy link
Contributor

inbelic commented Nov 20, 2024

The functions isVectorIntrinsicWithScalarOpAtArg and isVectorIntrinsicWithStructReturnOverloadAtField are unable to consider target specific intrinsics. This issue is resolved when these functions appropriately use the TTI impl when possible.

Essentially we want consistent behaviour with the changes here: #114849

AC:

  • Update isVectorIntrinsicWithScalarOpAtArg and isVectorIntrinsicWithStructReturnOverloadAtField to have a third parameter of TargetTransformInfo and to use this implementation when there is a target specific intrinsic. Update comment description of functions to include the new parameter
  • Update all uses-cases to pass in this argument
  • Remove the scalarizer functionality of isVectorIntrinsicWithScalarOpAtArg in Scalarizer.cpp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants