Fix max buffer requirement in no-memmove build#19
Merged
Conversation
Contributor
Author
|
float-check.cc only has white-space changes. A few negative subnormals tests are added to xjb-test.cc, and other changes are also white spaces. |
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
2 participants
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.
An overflow detected in ssrJSON's new encode fuzzer: dtoa(-1.5e-323), which triggers assertion failure at line 1460.
max_buffer_requirementmust be 33 even in no-memmove build.Also adds more tests to cover this case, and reformat src + test code.