Skip to content

Mark MINIMAL_RUNTIME_STREAMING_WASM_COMPILATION as requiring html output #24849

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

Merged
merged 1 commit into from
Aug 4, 2025

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Aug 1, 2025

The code for handling this setting and performing the streaming exists only in the generated html.

Also error out if MINIMAL_RUNTIME_STREAMING_WASM_* are used without MINIMAL_RUNTIME.

Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

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

Perhaps make this a warning and not an error? I don't feel strongly though.

The code for handling this setting and performing the streaming exists
only in the generated html.

Also error out if MINIMAL_RUNTIME_STREAMING_WASM_* are used without
MINIMAL_RUNTIME.
@sbc100
Copy link
Collaborator Author

sbc100 commented Aug 1, 2025

Perhaps make this a warning and not an error? I don't feel strongly though.

The problem is that if we do that then we have to consider that combination of options downstream in the rest of the code.

I guess we could invent a mechanism by which you could resolve incompatible options but disabled one of them with warning.. but we don't have that today. I think for everyone's sanity its best to ban outright these incompatible options.

@sbc100 sbc100 merged commit 03a8ee1 into emscripten-core:main Aug 4, 2025
28 of 30 checks passed
@sbc100 sbc100 deleted the streaming_wasm branch August 4, 2025 19:14
sbc100 added a commit to sbc100/emscripten that referenced this pull request Aug 5, 2025
This test updated in emscripten-core#24849 which caused the asan and lsan versions of
the test to start failing.  The reason is that prior to emscripten-core#24849 there was
a bug that caused the test not actually to be run via the santizers
since self.cflags was being assigned using `=` rather then `+=`.  This
was clobbering all the builtin cflags such as `-fsanitizer=address`.

Once emscripten-core#24849 this bug was fixed but that exposed another bug in the test
which is that it was not including the
`minimal_runtime_exit_handling.js` file.  Without this file included
tests that use MINIMAL_RUNTIME and EXIT_RUNTIME would see an unhandled
excpetion then the program exits (due to the `throw` of `exit(0)`).
sbc100 added a commit to sbc100/emscripten that referenced this pull request Aug 5, 2025
This test updated in emscripten-core#24849 which caused the asan and lsan versions of
the test to start failing.  The reason is that prior to emscripten-core#24849 there was
a bug that caused the test not actually to be run via the santizers
since self.cflags was being assigned using `=` rather then `+=`.  This
was clobbering all the builtin cflags such as `-fsanitizer=address`.

Once emscripten-core#24849 this bug was fixed but that exposed another bug in the test
which is that it was not including the
`minimal_runtime_exit_handling.js` file.  Without this file included
tests that use MINIMAL_RUNTIME and EXIT_RUNTIME would see an unhandled
excpetion then the program exits (due to the `throw` of `exit(0)`).
sbc100 added a commit that referenced this pull request Aug 5, 2025
This test updated in #24849 which caused the asan and lsan versions of
the test to start failing. The reason is that prior to #24849 there was
a bug that caused the test not actually to be run via the santizers
since self.cflags was being assigned using `=` rather then `+=`. This
was clobbering all the builtin cflags such as `-fsanitizer=address`.

Once #24849 this bug was fixed but that exposed another bug in the test
which is that it was not including the
`minimal_runtime_exit_handling.js` file. Without this file included
tests that use MINIMAL_RUNTIME and EXIT_RUNTIME would see an unhandled
excpetion then the program exits (due to the `throw` of `exit(0)`).
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.

2 participants