Fix LTO runs of test_nothrow_new_nogrow #20543
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.
This test was recently added in #20154 but has been failing on the emscripten-releases waterfall in thinlto modes.
I'm not sure exactly why, but it seems that perhaps when the value of
data
is not actually thinLTO simple removes the call the new/malloc? I'm not sure why this wasn't also failing under full LTO.