Skip to content

Conversation

@sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Nov 1, 2024

This involved using toIndexType in a few more places due to recent wasm64 changes requiring BitInt in more places.

Split out from #22773

@sbc100 sbc100 requested review from dschuff and kripken November 1, 2024 23:32
@sbc100 sbc100 enabled auto-merge (squash) November 1, 2024 23:32
@sbc100 sbc100 force-pushed the update_node branch 2 times, most recently from 9e6ce62 to 8c1dc1f Compare November 4, 2024 17:06
@sbc100 sbc100 force-pushed the update_node branch 2 times, most recently from a5bd5a0 to b4e6a0e Compare November 4, 2024 19:19
This involved using toIndexType in a few more places due to recent
wasm64 changes requiring BitInt in more places.

Split out from emscripten-core#22773
@sbc100 sbc100 disabled auto-merge November 4, 2024 21:23
@sbc100 sbc100 merged commit 2a5abb4 into emscripten-core:main Nov 4, 2024
23 of 28 checks passed
@sbc100 sbc100 deleted the update_node branch November 4, 2024 21:23
@dschuff
Copy link
Member

dschuff commented Nov 5, 2024

This seems to have broken the wasm64l tests on Chromium CI: https://ci.chromium.org/ui/p/emscripten-releases/builders/try/linux/b8732162502277725409/overview
Do we need to require node canary for those now too?

@dschuff
Copy link
Member

dschuff commented Nov 5, 2024

Actually no, of course we shouldn't; the whole point of wasm64l is to work on MVP...

sbc100 added a commit to sbc100/emscripten that referenced this pull request Nov 5, 2024
@sbc100
Copy link
Collaborator Author

sbc100 commented Nov 5, 2024

Fix is in #22853

dschuff pushed a commit that referenced this pull request Nov 5, 2024
@dschuff
Copy link
Member

dschuff commented Nov 5, 2024

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.

3 participants