misc/wasm: move wasm runtime files to lib/wasm #68840

Zxilly · 2024-08-12T06:03:33Z

Fixes #68024

gopherbot · 2024-08-12T06:12:04Z

This PR (HEAD: c033927) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-12T06:19:18Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T06:26:38Z

This PR (HEAD: fcd2241) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-12T06:34:04Z

Message from Zxilly Chou:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T13:17:11Z

Message from Dmitri Shuralyov:

Patch Set 2: Commit-Queue+1

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T13:17:11Z

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-08-12T13:05:07Z","revision":"d71a07f5aac158c4a79460ac10f5853c6c6f075c"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T13:24:41Z

Message from Dmitri Shuralyov:

Patch Set 2: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T13:24:42Z

Message from Go LUCI:

Patch Set 2:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-wasip1-wasm_wazero has failed with summary (view all results):

go on master (change 604696)

Build or test failure, click here for results.

To reproduce, try gomote repro 8739806625711078865.

Additional links for debugging:

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T13:24:42Z

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T14:03:06Z

This PR (HEAD: 9afa97b) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-12T14:18:09Z

Message from Zxilly Chou:

Patch Set 2:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T14:33:04Z

Message from Zxilly Chou:

Patch Set 3:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T15:32:26Z

Message from Dmitri Shuralyov:

Patch Set 3:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T16:40:15Z

Message from Johan Brandhorst-Satzkorn:

Patch Set 3:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T18:01:28Z

Message from Zxilly Chou:

Patch Set 3:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-12T18:53:13Z

This PR (HEAD: 25ff50c) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-13T00:44:18Z

Message from Dmitri Shuralyov:

Patch Set 4:

(4 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T11:32:59Z

This PR (HEAD: bb86099) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-13T11:40:10Z

Message from Zxilly Chou:

Patch Set 4:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T12:43:26Z

This PR (HEAD: d7c8657) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-13T12:50:53Z

Message from Zxilly Chou:

Patch Set 5:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T16:43:10Z

Message from Johan Brandhorst-Satzkorn:

Patch Set 6:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T16:58:36Z

This PR (HEAD: 5676260) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-13T17:06:01Z

Message from Zxilly Chou:

Patch Set 6:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T17:06:02Z

Message from Zxilly Chou:

Patch Set 6:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T18:05:31Z

Message from Johan Brandhorst-Satzkorn:

Patch Set 7:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T18:42:15Z

This PR (HEAD: 9825c86) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-13T18:56:49Z

Message from Zxilly Chou:

Patch Set 7:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-13T22:03:27Z

Message from Dmitri Shuralyov:

Patch Set 8: Code-Review+2 Commit-Queue+1

(5 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-19T22:28:32Z

Message from Johan Brandhorst-Satzkorn:

Patch Set 14:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-20T05:36:06Z

This PR (HEAD: 1ece807) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-20T05:42:31Z

Message from Zxilly Chou:

Patch Set 14:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-20T16:01:49Z

Message from Cherry Mui:

Patch Set 15:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-20T17:26:07Z

Message from Zxilly Chou:

Patch Set 15:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-20T17:26:15Z

This PR (HEAD: 9d921ed) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-20T17:33:32Z

This PR (HEAD: dff93a7) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-20T17:46:38Z

Message from Zxilly Chou:

Patch Set 15:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-21T20:08:40Z

This PR (HEAD: cad0954) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-23T20:32:09Z

Message from Cherry Mui:

Patch Set 19:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-23T20:38:37Z

Message from Dmitri Shuralyov:

Patch Set 19: Code-Review+2

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-24T08:39:43Z

Message from Zxilly Chou:

Patch Set 19:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-24T08:39:52Z

This PR (HEAD: 4242f36) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/604696.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-30T18:07:51Z

Message from Dmitri Shuralyov:

Patch Set 20: Code-Review+2 Commit-Queue+1

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-30T18:07:51Z

Message from Go LUCI:

Patch Set 20:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-08-30T17:59:39Z","revision":"b7bea45edf980c511efaa408c8b9d97f1b70f2c9"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-30T18:22:04Z

Message from Cherry Mui:

Patch Set 20: Code-Review+2

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-30T18:22:04Z

Message from Dmitri Shuralyov:

Patch Set 20: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-30T18:22:05Z

Message from Go LUCI:

Patch Set 20:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-30T18:22:05Z

Message from Go LUCI:

Patch Set 20: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

Fixes #68024 Change-Id: I730c3ecfb14472f3eea3895c2a4d5e1d4ac146f5 GitHub-Last-Rev: 4242f36 GitHub-Pull-Request: #68840 Reviewed-on: https://go-review.googlesource.com/c/go/+/604696 Reviewed-by: Cherry Mui <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Johan Brandhorst-Satzkorn <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>

gopherbot · 2024-08-30T19:18:52Z

Message from Dmitri Shuralyov:

Patch Set 20: Auto-Submit+1

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/604696.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-08-30T19:26:28Z

This PR is being closed because golang.org/cl/604696 has been merged.

Zxilly force-pushed the wasm/runtime branch from 5676260 to 9825c86 Compare August 13, 2024 18:41

Zxilly force-pushed the wasm/runtime branch from 1ece807 to 9d921ed Compare August 20, 2024 17:23

Zxilly force-pushed the wasm/runtime branch from 9d921ed to dff93a7 Compare August 20, 2024 17:27

Zxilly force-pushed the wasm/runtime branch from dff93a7 to 1ece807 Compare August 20, 2024 17:35

Zxilly added 2 commits August 22, 2024 04:03

misc/wasm: move wasm runtime files to lib/wasm

27e94a8

move back

cad0954

Zxilly force-pushed the wasm/runtime branch from 1ece807 to cad0954 Compare August 21, 2024 20:03

update

4242f36

gopherbot closed this Aug 30, 2024

misc/wasm: move wasm runtime files to lib/wasm #68840

misc/wasm: move wasm runtime files to lib/wasm #68840

Conversation

Zxilly commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 12, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 13, 2024

gopherbot commented Aug 19, 2024

gopherbot commented Aug 20, 2024

gopherbot commented Aug 20, 2024

gopherbot commented Aug 20, 2024

gopherbot commented Aug 20, 2024

gopherbot commented Aug 20, 2024

gopherbot commented Aug 20, 2024

gopherbot commented Aug 20, 2024

gopherbot commented Aug 21, 2024

gopherbot commented Aug 23, 2024

gopherbot commented Aug 23, 2024

gopherbot commented Aug 24, 2024

gopherbot commented Aug 24, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024