runtime: add ERMS-based memmove support for modern CPU platforms #66959

cocotyty · 2024-04-22T09:11:54Z

The current memmove implementation uses REP MOVSB to copy data larger than
2KB when the useAVXmemmove global variable is false and the CPU supports
the ERMS feature.

This feature is currently only enabled on CPUs in the Sandy Bridge (Client)
, Sandy Bridge (Server), Ivy Bridge (Client), and Ivy Bridge (Server)
microarchitectures.

For modern Intel CPU microarchitectures that support the ERMS feature, such
as Ice Lake (Server), Sapphire Rapids , REP MOVSB achieves better
performance than the AVX-based copy currently implemented in memmove.

Benchstat result:

goos: linux
goarch: amd64
pkg: runtime
cpu: Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz
│ ./old.txt │ ./new.txt │
│ sec/op │ sec/op vs base │
Memmove/2048-2 25.24n ± 0% 24.27n ± 0% -3.84% (p=0.000 n=10)
Memmove/4096-2 44.87n ± 0% 33.16n ± 1% -26.11% (p=0.000 n=10)
geomean 33.65n 28.37n -15.71%

           │  ./old.txt   │               ./new.txt               │
           │     B/s      │      B/s       vs base                │

Memmove/2048-2 75.56Gi ± 0% 78.59Gi ± 0% +4.02% (p=0.000 n=10)
Memmove/4096-2 85.01Gi ± 0% 115.05Gi ± 1% +35.34% (p=0.000 n=10)
geomean 80.14Gi 95.09Gi +18.65%

Fixes #66958

gopherbot · 2024-04-22T09:20:58Z

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

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

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-04-22T09:27:29Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T09:27:29Z

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://go.dev/s/release
for more details.

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

gopherbot · 2024-04-22T10:45:47Z

Message from qiulaidongfeng:

Patch Set 1: Commit-Queue+1

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

gopherbot · 2024-04-22T10:52:35Z

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-22T10:39:48Z","revision":"d49514407921eb0754bda55d3aae8e71336c9fa2"}

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

gopherbot · 2024-04-22T11:11:40Z

Message from qiulaidongfeng:

Patch Set 1: -Commit-Queue

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

gopherbot · 2024-04-22T11:11:40Z

Message from Go LUCI:

Patch Set 1:

This CL has passed the run

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

gopherbot · 2024-04-22T11:11:41Z

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result+1

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

gopherbot · 2024-04-22T14:46:16Z

Message from Keith Randall:

Patch Set 1:

(2 comments)

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

gopherbot · 2024-04-22T14:59:34Z

Message from Martin Möhrmann:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T14:59:34Z

Message from Martin Möhrmann:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T15:13:42Z

Message from Alexander Yastrebov:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T15:33:03Z

Message from Keith Randall:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T15:59:13Z

Message from Martin Möhrmann:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T17:05:06Z

Message from Mauri de Souza Meneguzzo:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T17:11:26Z

Message from Dmitry Vyukov:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-04-22T17:38:14Z

Message from Martin Möhrmann:

Patch Set 1:

(1 comment)

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

gopherbot · 2024-05-13T08:01:41Z

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

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

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-05-14T18:01:46Z

Message from Keith Randall:

Patch Set 2:

(1 comment)

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

gopherbot · 2024-05-17T07:05:33Z

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

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

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-05-17T15:27:53Z

Message from Keith Randall:

Patch Set 3:

(2 comments)

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

gopherbot · 2024-05-20T09:11:17Z

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

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

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-05-29T19:30:07Z

Message from Martin Möhrmann:

Patch Set 6:

(1 comment)

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

gopherbot · 2024-05-30T01:57:45Z

Message from 唐阳:

Patch Set 6:

(7 comments)

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

gopherbot · 2024-06-03T10:18:46Z

Message from Martin Möhrmann:

Patch Set 6:

(2 comments)

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

gopherbot · 2024-06-04T05:43:27Z

Message from 唐阳:

Patch Set 6:

(2 comments)

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

gopherbot · 2024-06-04T06:04:32Z

Message from Martin Möhrmann:

Patch Set 6:

(1 comment)

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

gopherbot · 2024-06-21T15:03:11Z

Message from Keith Randall:

Patch Set 12: -Commit-Queue

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

gopherbot · 2024-06-21T15:03:11Z

Message from Go LUCI:

Patch Set 12:

This CL has passed the run

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

gopherbot · 2024-06-21T15:03:12Z

Message from Go LUCI:

Patch Set 12: LUCI-TryBot-Result+1

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

gopherbot · 2024-06-23T04:49:35Z

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

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

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-06-27T13:02:25Z

Message from 唐阳:

Patch Set 13:

(5 comments)

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

gopherbot · 2024-06-27T14:45:53Z

Message from Keith Randall:

Patch Set 13: Code-Review+2

(1 comment)

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

gopherbot · 2024-06-27T14:45:53Z

Message from Keith Randall:

Patch Set 13: Code-Review+1

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

gopherbot · 2024-06-27T15:19:37Z

Message from Cherry Mui:

Patch Set 13: Code-Review+1

(2 comments)

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

gopherbot · 2024-06-27T15:53:04Z

Message from 唐阳:

Patch Set 13:

(1 comment)

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

gopherbot · 2024-06-27T15:59:39Z

Message from 唐阳:

Patch Set 13:

(1 comment)

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

gopherbot · 2024-06-27T16:25:10Z

Message from Cherry Mui:

Patch Set 13:

(2 comments)

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

gopherbot · 2024-06-28T14:36:01Z

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

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

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-07-01T07:17:32Z

Message from 唐阳:

Patch Set 14:

(2 comments)

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

gopherbot · 2024-07-01T11:02:30Z

Message from qiu laidongfeng2:

Patch Set 14: Commit-Queue+1

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

gopherbot · 2024-07-01T11:02:30Z

Message from Go LUCI:

Patch Set 14:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-07-01T10:57:31Z","revision":"cd0acea9605c5cb256d2dca3a31c0ed06bb2700f"}

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

gopherbot · 2024-07-01T11:09:09Z

Message from qiu laidongfeng2:

Patch Set 14: -Commit-Queue

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

gopherbot · 2024-07-01T11:09:10Z

Message from Go LUCI:

Patch Set 14:

This CL has failed the run. Reason:

Tryjob golang/try/x_tools-gotip-linux-amd64 has failed with summary (view all results):

go on master (change 580735)
tools on master (commit fcf5463)

Build or test failure, click here for results.

Additional links for debugging:

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

gopherbot · 2024-07-01T11:09:10Z

Message from Go LUCI:

Patch Set 14: LUCI-TryBot-Result-1

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

The current memmove implementation uses REP MOVSB to copy data larger than 2KB when the useAVXmemmove global variable is false and the CPU supports the ERMS feature. This feature is currently only enabled on CPUs in the Sandy Bridge (Client) , Sandy Bridge (Server), Ivy Bridge (Client), and Ivy Bridge (Server) microarchitectures. For modern Intel CPU microarchitectures that support the ERMS feature, such as Ice Lake (Server), Sapphire Rapids , REP MOVSB achieves better performance than the AVX-based copy currently implemented in memmove. Benchstat result: goos: linux goarch: amd64 pkg: runtime cpu: Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz │ ./old.txt │ ./new.txt │ │ sec/op │ sec/op vs base │ Memmove/2048-2 25.24n ± 0% 24.27n ± 0% -3.84% (p=0.000 n=10) Memmove/4096-2 44.87n ± 0% 33.16n ± 1% -26.11% (p=0.000 n=10) geomean 33.65n 28.37n -15.71% │ ./old.txt │ ./new.txt │ │ B/s │ B/s vs base │ Memmove/2048-2 75.56Gi ± 0% 78.59Gi ± 0% +4.02% (p=0.000 n=10) Memmove/4096-2 85.01Gi ± 0% 115.05Gi ± 1% +35.34% (p=0.000 n=10) geomean 80.14Gi 95.09Gi +18.65% Fixes golang#66958 Signed-off-by: TangYang <[email protected]>

gopherbot · 2024-07-02T04:02:18Z

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

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

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-07-02T05:15:10Z

Message from Keith Randall:

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

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

gopherbot · 2024-07-02T05:21:07Z

Message from Go LUCI:

Patch Set 15:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-07-02T05:10:01Z","revision":"f67e5a9acf04f5bbba18bf0f81c5f3ec7efbc208"}

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

gopherbot · 2024-07-02T05:41:37Z

Message from Keith Randall:

Patch Set 15: -Commit-Queue

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

gopherbot · 2024-07-02T05:41:38Z

Message from Go LUCI:

Patch Set 15:

This CL has passed the run

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

gopherbot · 2024-07-02T05:41:38Z

Message from Go LUCI:

Patch Set 15: LUCI-TryBot-Result+1

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

gopherbot · 2024-07-02T17:17:31Z

Message from Keith Randall:

Patch Set 15: Auto-Submit+1

(1 comment)

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

The current memmove implementation uses REP MOVSB to copy data larger than 2KB when the useAVXmemmove global variable is false and the CPU supports the ERMS feature. This feature is currently only enabled on CPUs in the Sandy Bridge (Client) , Sandy Bridge (Server), Ivy Bridge (Client), and Ivy Bridge (Server) microarchitectures. For modern Intel CPU microarchitectures that support the ERMS feature, such as Ice Lake (Server), Sapphire Rapids , REP MOVSB achieves better performance than the AVX-based copy currently implemented in memmove. Benchstat result: goos: linux goarch: amd64 pkg: runtime cpu: Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz │ ./old.txt │ ./new.txt │ │ sec/op │ sec/op vs base │ Memmove/2048-2 25.24n ± 0% 24.27n ± 0% -3.84% (p=0.000 n=10) Memmove/4096-2 44.87n ± 0% 33.16n ± 1% -26.11% (p=0.000 n=10) geomean 33.65n 28.37n -15.71% │ ./old.txt │ ./new.txt │ │ B/s │ B/s vs base │ Memmove/2048-2 75.56Gi ± 0% 78.59Gi ± 0% +4.02% (p=0.000 n=10) Memmove/4096-2 85.01Gi ± 0% 115.05Gi ± 1% +35.34% (p=0.000 n=10) geomean 80.14Gi 95.09Gi +18.65% Fixes #66958 Change-Id: I1fafd1b51a16752f83ac15047cf3b29422a79d5d GitHub-Last-Rev: 89cf5af GitHub-Pull-Request: #66959 Reviewed-on: https://go-review.googlesource.com/c/go/+/580735 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Keith Randall <[email protected]> Reviewed-by: Keith Randall <[email protected]> Auto-Submit: Keith Randall <[email protected]> Reviewed-by: Cherry Mui <[email protected]>

gopherbot · 2024-07-22T21:29:54Z

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

cocotyty changed the title ~~Add Ice Lake and Sapphire Rapids ERMS support~~ runtime: Add Ice Lake and Sapphire Rapids ERMS support for memmove Apr 22, 2024

cocotyty force-pushed the master branch from 8c00c8b to 7f7e861 Compare May 13, 2024 07:58

cocotyty changed the title ~~runtime: Add Ice Lake and Sapphire Rapids ERMS support for memmove~~ runtime: add ERMS-based memmove support for modern CPU platforms May 27, 2024

cocotyty force-pushed the master branch from 5d3dfcb to 89cf5af Compare July 2, 2024 03:58

gopherbot closed this Jul 22, 2024

runtime: add ERMS-based memmove support for modern CPU platforms #66959

runtime: add ERMS-based memmove support for modern CPU platforms #66959

Conversation

cocotyty commented Apr 22, 2024 • edited Loading

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented Apr 22, 2024

gopherbot commented May 13, 2024

gopherbot commented May 14, 2024

gopherbot commented May 17, 2024

gopherbot commented May 17, 2024

gopherbot commented May 20, 2024

gopherbot commented May 29, 2024

gopherbot commented May 30, 2024

gopherbot commented Jun 3, 2024

gopherbot commented Jun 4, 2024

gopherbot commented Jun 4, 2024

gopherbot commented Jun 21, 2024

gopherbot commented Jun 21, 2024

gopherbot commented Jun 21, 2024

gopherbot commented Jun 23, 2024

gopherbot commented Jun 27, 2024

gopherbot commented Jun 27, 2024

gopherbot commented Jun 27, 2024

gopherbot commented Jun 27, 2024

gopherbot commented Jun 27, 2024

gopherbot commented Jun 27, 2024

gopherbot commented Jun 27, 2024

gopherbot commented Jun 28, 2024

gopherbot commented Jul 1, 2024

gopherbot commented Jul 1, 2024

gopherbot commented Jul 1, 2024

gopherbot commented Jul 1, 2024

gopherbot commented Jul 1, 2024

gopherbot commented Jul 1, 2024

gopherbot commented Jul 2, 2024

gopherbot commented Jul 2, 2024

gopherbot commented Jul 2, 2024

gopherbot commented Jul 2, 2024

gopherbot commented Jul 2, 2024

gopherbot commented Jul 2, 2024

gopherbot commented Jul 2, 2024

gopherbot commented Jul 22, 2024

cocotyty commented Apr 22, 2024 •

edited

Loading