float printing was lossy in 2 places, fix this#1306
Merged
Conversation
Contributor
Author
|
here's an example that justifies both parts of this patch: define float @test_float_fdiv_pzero_f32_out() #0 {
%result = fdiv float 0x3810000000000000, -2.000000e+00
ret float %result
}
attributes #0 = { denormal_fpenv(positivezero|ieee) }current alive2: alive2 with this patch: |
Contributor
Author
|
btw I think it's not LLVM who's wrong on this example, it's us |
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.
ok let's try this again. the problem was in
to_string(fp)-- this is lossy, it does not faithfully print the value. this patch should result in fully round-trippable float printing.there was an analogous problem in CEX printing, this fixes that too