Skip to content

Conversation

@aheejin
Copy link
Member

@aheejin aheejin commented May 15, 2024

We settled on the name WASM_EXNREF for the new setting in Emscripten for the name for the new EH option.
https://github.com/emscripten-core/emscripten/blob/2bc5e3156f07e603bc4f3580cf84c038ea99b2df/src/settings.js#L782-L786 "New EH" sounds vague and I'm not sure if "experimental" is really necessary anyway, given that the potential users of this option is aware that this is a new spec that has been adopted recently.

To make the option names consistent, this renames --translate-to-eh (the option that only runs the translator) to --translate-to-exnref, and --experimental-new-eh to --emit-exnref (the option that runs the translator at the end of the whole pipeline), and renames the pass and variable names in the code accordingly as well.

In case anyone is using the old option names (and also to make the Chromium CI pass), this does not delete the old options.

We settled on the name `WASM_EXNREF` for the new setting in Emscripten
for the name for the new EH option.
https://github.com/emscripten-core/emscripten/blob/2bc5e3156f07e603bc4f3580cf84c038ea99b2df/src/settings.js#L782-L786
"New EH" sounds vague and I'm not sure if "experimental" is really
necessary anyway, given that the potential users of this option is aware
that this is a new spec that has been adopted recently.

To make the option names consistent, this renames `--translate-to-eh`
(the option that only runs the translator) to `--translate-to-exnref`,
and `--experimental-new-eh` to `--emit-exnref` (the option that runs the
translator at the end of the whole pipeline), and renames the pass and
variable names in the code accordingly as well.

In case anyone is using the old option names (and also to make the
Chromium CI pass), this does not delete the old options.
@aheejin aheejin requested review from kripken and tlively May 15, 2024 01:56
@@ -0,0 +1,28 @@
;; When given alone, --emit-exnref just runs --translate-to-exnref
Copy link
Member Author

@aheejin aheejin May 15, 2024

Choose a reason for hiding this comment

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

This file has been moved from experimental-new_eh.wast. Not sure why it is not recognized as such.

aheejin added a commit to aheejin/emscripten that referenced this pull request May 15, 2024
This option was renamed in Binaryen to be consistent with the
corresponding Emscripten option `-sWASM_EXNREF`:
WebAssembly/binaryen#6592

The CI will pass once WebAssembly/binaryen#6592
passes the Chromium CI.
@aheejin aheejin merged commit ae94994 into WebAssembly:main May 15, 2024
@aheejin aheejin deleted the wasm_exnref branch May 15, 2024 19:36
aheejin added a commit to emscripten-core/emscripten that referenced this pull request May 16, 2024
This option was renamed in Binaryen to be consistent with the
corresponding Emscripten option `-sWASM_EXNREF`:
WebAssembly/binaryen#6592

The CI will pass once WebAssembly/binaryen#6592
passes the Chromium CI.
@gkdn gkdn mentioned this pull request Aug 31, 2024
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