Skip to content

[NFC] Some comments in settings.js #17410

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 2 commits into from
Jul 11, 2022
Merged

[NFC] Some comments in settings.js #17410

merged 2 commits into from
Jul 11, 2022

Conversation

kripken
Copy link
Member

@kripken kripken commented Jul 11, 2022

No description provided.

@kripken kripken requested a review from sbc100 July 11, 2022 19:51
// [link]
var MIN_EDGE_VERSION = 44;

// Specifies the oldest version of Chrome. E.g. pass -sMIN_CHROME_VERSION=58 to
// drop support for Chrome 57 and older.
// Chrome 75.0.3770 was released on 2019-06-04
// MAX_INT (0x7FFFFFFF, or -1) specifies that target is not supported.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does -1 really work? If so maybe just stick to that and drop the 0x7FFFFFFF magic?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, it does work. We have code to convert them in emcc.py.

I agree it makes sense to simplify this, and -1 is probably better. I can look into that as a followup.

Copy link
Member Author

Choose a reason for hiding this comment

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

Or I guess this is so small I could wait and do it here.

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh, reading the emcc.py code, it is necessary to use 0x7fffffff, as it's a large positive number, which the code depends on. So we just have some parsing support for -1 that we turn it into 0x7fffffff, but use the latter internally. Not sure that makes sense to change.

@kripken kripken merged commit fceb56a into main Jul 11, 2022
@kripken kripken deleted the comment branch July 11, 2022 20:17
xbcnn pushed a commit to xbcnn/emscripten that referenced this pull request Jul 22, 2022
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