-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Conversation
There was a problem hiding this 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.
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. |
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)`).
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)`).
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)`).
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.