Skip to content
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

Remove some remaining internal uses of the old USE_PTHREADS settings #19474

Merged
merged 1 commit into from
May 30, 2023

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented May 30, 2023

These were not showing up in tests because they only show up with -sSTRICT + -O2 (or above).

I'm not sure how I missed them in #18923. My guess is that they might have shown up as part of later commits.

Fixes: #19471

… NFC

These were not showing up in tests because they only show up with
`-sSTRICT` + `-O2` (or above).

I'm not sure how I missed them in #18923.  My guess is that they might
have shown up as part of later commits.

Fixes: #19471
@sbc100 sbc100 requested a review from kripken May 30, 2023 20:46
@sbc100 sbc100 force-pushed the remove_use_pthreads_usage branch from e8bc71c to eebbead Compare May 30, 2023 20:46
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.

lgtm % comment

@@ -10042,6 +10042,7 @@ def test_minimal_runtime_code_size(self, test_name, js, compare_js_output=False)
'-sMIN_CHROME_VERSION=58',
'-sGL_WORKAROUND_SAFARI_GETCONTEXT_BUG=0',
'-sNO_FILESYSTEM',
'-sSTRICT',
Copy link
Member

Choose a reason for hiding this comment

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

Why add this? I'd think the opposite is better as it's closer to what most users do.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This test is all about specifying as many non-default settings as possible in order to minimize code size. While adding -sSTRICT here doesn't currently shave any bytes of the code size one could imagine that it could reasonable do this (imagine a case where we need to include legacy support for something, but we can avoid doing that in strict mode).

Adding this setting here triggers all the code paths where the old name (USE_PTHREADS) was incorrectly used internally (but ignored because of we allow the old name to be used as an alias by default).

In other words, this change is what actually tests that I've fixed the bug.

Copy link
Member

Choose a reason for hiding this comment

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

I see. Sounds good!

@sbc100 sbc100 merged commit 0fb0c7a into main May 30, 2023
@sbc100 sbc100 deleted the remove_use_pthreads_usage branch May 30, 2023 22:24
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.

-sUSE_PTHREADS is simultaneously required and deprecated
2 participants