-
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
Identical function types not merged #3989
Comments
Interesting find! I would expect issues like this with nominal typing enabled, but not with the default equirecursive typing. Will investigate. |
kripken
added a commit
that referenced
this issue
Aug 5, 2021
kripken
added a commit
that referenced
this issue
Aug 5, 2021
18 tasks
This no longer seems to reproduce after switching to the new parser and making a bunch of other changes that might have been related. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
STR:
wasm-opt w.wasm -all --print --name-types --print
The output is
The key thing is the
$none_=>_none
type, which should not exist after we name the types. It appears twice in the element segments, and remains in one of them at the end. It seems that the two may have gotten different types..?cc @tlively
(found by fuzzer seed
9943180413750209438
, then reduced. it can't be reduced by hand as the bug does not show itself on the text format...)w.wasm.gz
The text was updated successfully, but these errors were encountered: