AOT: Fix NaN handling for f32/f64 const op #3721
Merged
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
no1wudi
force-pushed
the
riscv
branch
3 times, most recently
from
521b094 to
bbb76ad
Compare
no1wudi
force-pushed
the
riscv
branch
5 times, most recently
from
0fcf99a to
eeca2d6
Compare
If the value of a float constant is NaN, it will not be handed correctly by f32.const or f64.const, then it may cause a relocation in the AOT file.
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.
If the value of a float constant is NaN, it will not be handed correctly by f32.const or f64.const, then it may cause a relocation in the AOT file.