fpu: implement Zfa minimum-number-or-NaN operations - #298
Open
carlosqwqqwq wants to merge 1 commit into
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fpu: implement Zfa minimum-number-or-NaN operations
Fixes #295
Commit message
Description
The Zfa
fminm/fmaxminstructions currently call the IEEE-754-2008fmin/fmaxhelpers. Those helpers return the numeric operand when one input is NaN, but the minimum-number-or-NaN instructions must return canonical NaN when either input is NaN. Add precision-specific helpers and preserve the existing numeric ordering and signaling-NaN flag behavior.Validation
qemu-riscv64, Zfa) returns the canonical qNaN whenever either input is NaN; the patched build matches on the single- and double-precision one-NaN and two-NaN witnesses. The native reference does not implement Zfa and is recorded as a capability boundary.