Skip to content

Conversation

@kripken
Copy link
Member

@kripken kripken commented May 29, 2018

See #1479 (comment)

Also a one-line readme update, remove an obsolete compiler (mir2wasm) and add a new one (asterius).

@kripken kripken mentioned this pull request May 29, 2018
@kripken
Copy link
Member Author

kripken commented May 29, 2018

Also added a line to customize how we exit on fatal errors - instead of letting node call process.exit which exits silently, show a stack trace.

Copy link
Contributor

@jgravelle-google jgravelle-google left a comment

Choose a reason for hiding this comment

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

lgtm

@kripken
Copy link
Member Author

kripken commented Jul 9, 2018

I finally found time to rebase this and fix the test issue. The problem there was that the -g builds on the bots had assertions enabled, which cluttered the output. I removed assertions by default there.

kripken added 2 commits July 9, 2018 14:23
…r atexits in binaryen.js, we just don't want those warnings cluttering us up
@kripken
Copy link
Member Author

kripken commented Jul 10, 2018

I found a way to work around the test issue, by just disabling the atexit() assertion messages in binaryen.js, instead of disabling all assertions in non-optimized builds.

@kripken kripken merged commit 5ccfbac into master Jul 10, 2018
@kripken kripken deleted the error-handling branch July 10, 2018 18:05
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.

3 participants