Closed
Conversation
Member
|
I'm very looking forward to seeing this PR merged. Thank you for your efforts! 👍 |
Member
Author
|
There is still the problem of it breaking Chrome CI to deal with... |
Member
Author
|
Okay, I think this is in good shape now:
|
Member
Author
|
Closed in favor of #2019. |
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.
A second, much simpler approach to handling the bad fpcasts.
There are only a few problematic call sites, so just patch call trampolines into the interpreter at these locations.