Repository navigation
Conversation
tlively
approved these changes
Oct 16, 2026
| // | ||
| // The only case where we are always ok to remove such casts is when lastOpts | ||
| // is true, because nothing significant runs after us that can be harmed. That | ||
| // logic is in the StripRefiningCasts pass. |
Member
Author
|
Unfortunately this is not enough, as VM differences in grow success now show up (due to the new testcase). I suppose we just need to limit memory sizes in the fuzzer... |
Member
Author
|
Closing in favor of #9269 |
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.
memory.growof 0 changes nothing and just returns the old size. On thefuzzer this was erroring, as we did reallocate and OOMed, while v8 did
not.