Only run --no-exit-runtime when optimizing #11998
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
That pass is a pure optimization: it removes calls to
atexit
when theywould be ignored anyhow (
EXIT_RUNTIME == 0
).This removes a warning in
atexit
's implementation that was neveractually called before: we used to always run that pass, so if
EXIT_RUNTIME == 0
then we never had any calls toatexit
anyhow. Now that we only run the pass when optimizing, leaving
that warning would be a noticeable change (and it broke some
tests actually!) so just remove it. With that, this is essentially
NFC except that non-optimized builds may be a little larger
(containing calls to
atexit
that end up doing nothing).Helps WebAssembly/binaryen#3043