Skip to content

Cherry-pick to 5.4 branch: [WASM] Fix KeyPath optimization bug around signature match #3335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

kateinoigakukun
Copy link
Member

ref: #3334

For wasm, KeyPath getter always take indices parameter to match callee
and caller signature. So need to pass stub pointer.
@MaxDesiatov
Copy link

Do we have CI set up for 5.4 at all? Looks like no checks are going to run here

Copy link

@MaxDesiatov MaxDesiatov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kateinoigakukun
Copy link
Member Author

OK, ready to land!

@MaxDesiatov
Copy link

Sure, feel free to merge 🙂

@kateinoigakukun kateinoigakukun merged commit d78fdc2 into swiftwasm-release/5.4 Aug 6, 2021
@kateinoigakukun kateinoigakukun deleted the katei/cherry-pick-5.4-81751d916802dd6c0f9bbff32a0f902f1bae5d14 branch August 6, 2021 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants