internal/bytealg: unroll compare_arm64.s chunk16_loop to 32 bytes/iter

[mauri870]

goos: darwin
goarch: arm64
pkg: bytes
cpu: Apple M3 Pro
│ old.txt │ new.txt │
│ sec/op │ sec/op vs base │
CompareBytesBigUnaligned/offset=1-11 26.44µ ± 0% 22.91µ ± 1% -13.36% (p=0.000 n=10)
CompareBytesBigUnaligned/offset=2-11 26.43µ ± 0% 22.90µ ± 0% -13.33% (p=0.000 n=10)
CompareBytesBigUnaligned/offset=3-11 26.42µ ± 1% 22.90µ ± 1% -13.32% (p=0.000 n=7+10)
CompareBytesBigUnaligned/offset=4-11 22.92µ ± ∞ ¹
geomean 26.43µ 22.91µ -13.34%
¹ need >= 6 samples for confidence interval at level 0.95

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

CompareBytesBigUnaligned/offset=1-11 36.94Gi ± 0% 42.63Gi ± 1% +15.41% (p=0.000 n=10)
CompareBytesBigUnaligned/offset=2-11 36.96Gi ± 0% 42.64Gi ± 0% +15.39% (p=0.000 n=10)
CompareBytesBigUnaligned/offset=3-11 36.97Gi ± 1% 42.65Gi ± 1% +15.37% (p=0.000 n=7+10)
CompareBytesBigUnaligned/offset=4-11 42.60Gi ± ∞ ¹
geomean 36.95Gi 42.63Gi +15.39%

[gopherbot]

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

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

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]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

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

[gopherbot]

Message from Mauri de Souza Meneguzzo:

Patch Set 1:

(1 comment)

---

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

[gopherbot]

Message from Mauri de Souza Meneguzzo:

Patch Set 1: Commit-Queue+1

---

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

[gopherbot]

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2026-05-28T20:22:57Z","revision":"18633880d57fadf146e453bec52edcc77188d8a3"}

---

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

[gopherbot]

Message from Mauri de Souza Meneguzzo:

Patch Set 1: -Commit-Queue

(Performed by <GERRIT_ACCOUNT_60063> on behalf of <GERRIT_ACCOUNT_63983>)

---

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

[gopherbot]

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 1:

This CL has passed the run

---

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

[gopherbot]

Message from golang-scoped@luci-project-accounts.iam.gserviceaccount.com:

Patch Set 1: LUCI-TryBot-Result+1

---

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

[gopherbot]

Message from Keith Randall:

Patch Set 1:

(1 comment)

---

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

[gopherbot]

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

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

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]

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

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

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]

Message from Mauri de Souza Meneguzzo:

Patch Set 2:

(1 comment)

---

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

[gopherbot]

Message from Keith Randall:

Patch Set 4: Code-Review+2

(2 comments)

---

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