-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Expose the FusedMultiplyAdd and MultiplyAddEstimate APIs on relevant vector and scalar types #102181
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
Merged
Merged
Expose the FusedMultiplyAdd and MultiplyAddEstimate APIs on relevant vector and scalar types #102181
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
46caa78
Expose FusedMultiplyAdd and MultiplyAddEstimate on the scalar and vec…
tannergooding 940862e
Adding tests covering FusedMultiplyAdd and MultiplyAddEstimate for th…
tannergooding d5b2ad9
Ensure TensorPrimitives uses the xplat APIs on .NET 9+
tannergooding 731258f
Apply formatting patch
tannergooding 4010235
Fix an accidental change to GenericVectorTests
tannergooding 8a60cff
Ensure Arm64 passes fma operands in the correct order
tannergooding 5e1e5eb
Apply formatting patch
tannergooding 85425c2
Ensure all the Arm64 code paths are spilling and swapping operands
tannergooding 0896be6
Apply formatting patch
tannergooding fdd2a83
Don't pop the stack value twice
tannergooding File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Ensure Arm64 passes fma operands in the correct order
- Loading branch information
commit 8a60cff4f43b062c057e8055bd65f0835d000f2a
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 am just curious - who's responsible to spill them?
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.
Ah, nvm, I see
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.
Typically it's the importer code, prior to calling this method. Latter phases that might call such an API (like morph) are responsible for ensuring the swap is safe in the face of potential side effects.
There's, unfortunately, not really a way for us to do such a swap safely in the API itself (at least that I know of) nor to know if the caller has actually done it. So the typical approach has been to do the swap and comment that callers should be doing the validation.