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
CLI flag for accepting default visibility #947
Comments
As for the |
@pipcet thanks I managed to get the s2wasm tests to pass that way.
(The above is just my local setup obviously)... |
That looks like a clang-vs-gcc issue (as used for building binaryen, not for the wasm code :-) ). Does it happen with the vanilla tree? It might be worth filing a separate issue for that. |
I've implemented this on top of #587 as well as rebasing at master...guybedford:no-export-hidden-update.
This supports the default behaviour of
s2wasm
, but then providess2wasm --defaultVisibility
to enable the behaviour from #587.I didn't want to provide a PR, as these seem restricted by the contribution guidelines, but it's working well for me. Just let me know if a PR might be suitable (if I've even done this right!).
Note that when running
./check.py
I'm getting the error -so wasn't able to verify the tests.
The text was updated successfully, but these errors were encountered: