-
Notifications
You must be signed in to change notification settings - Fork 745
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
When creating dynCall
and legalstub
function mark them as hasExplicitName. NFC
#6496
Conversation
…icitName. NFC This is temporary workaround for the current test failures on the emscripten waterfall. The real fix I believe will be to make `hasExplicitName` the default in these kinds of cases. See: #6466
dynCall
and legalstub
function mark them as hasExpl…dynCall
and legalstub
function mark them as hasExplicitName. NFC
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a test? FWIW I took a stab at setting this in makeFunction
like @kripken suggested, but I couldn't see any effect on a roundtripping test, so I must have been missing something.
What do you think about just landing this now to make the emscripten CI green again and then followup with test as part of the |
Did you at least verify locally that it does fix the Emscripten issue? If so, I guess landing this would be ok. |
Yes I verified that this fixes the emscripten tests. |
I'm happy to start looking into tests and a better fix right away. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, thanks!
This is temporary workaround for the current test failures on the emscripten waterfall. The real fix I believe will be to make
hasExplicitName
the default in these kinds of cases.See: #6466