Skip to content

chacha20poly1305: correct AVX2 feature detection #44

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

Closed
wants to merge 1 commit into from
Closed

chacha20poly1305: correct AVX2 feature detection #44

wants to merge 1 commit into from

Conversation

tmthrgd
Copy link
Contributor

@tmthrgd tmthrgd commented May 2, 2018

CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

@gopherbot
Copy link
Contributor

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

Please visit https://go-review.googlesource.com/#/c/crypto/+/110796 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1:

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

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#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, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


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

@gopherbot
Copy link
Contributor

Message from Tobias Klauser:

Patch Set 1:

(1 comment)

Thanks.


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

@gopherbot
Copy link
Contributor

Message from Tobias Klauser:

Patch Set 1: Run-TryBot+1


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

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1:

TryBots beginning. Status page: https://farmer.golang.org/try?commit=f1e186ce


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

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1:

Build is still in progress...
This change failed on linux-amd64:
See https://storage.googleapis.com/go-build-log/500d79c4/linux-amd64_2d60c2a9.log

Consult https://build.golang.org/ to see whether it's a new failure. Other builds still in progress; subsequent failure notices suppressed until final report.


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

@gopherbot
Copy link
Contributor

Message from Tobias Klauser:

Patch Set 1:

Patch Set 1:

Build is still in progress...
This change failed on linux-amd64:
See https://storage.googleapis.com/go-build-log/500d79c4/linux-amd64_2d60c2a9.log

Consult https://build.golang.org/ to see whether it's a new failure. Other builds still in progress; subsequent failure notices suppressed until final report.

TryBot failure is unrelated, see https://golang.org/issue/25199


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

@gopherbot
Copy link
Contributor

Message from Tom Thorogood:

Patch Set 1:

Patch Set 1:

Build is still in progress...
This change failed on linux-amd64:
See https://storage.googleapis.com/go-build-log/500d79c4/linux-amd64_2d60c2a9.log

Consult https://build.golang.org/ to see whether it's a new failure. Other builds still in progress; subsequent failure notices suppressed until final report.

This is just golang/go#25199 right?


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

@gopherbot
Copy link
Contributor

Message from Tom Thorogood:

Patch Set 2: Commit message was updated.


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

@gopherbot
Copy link
Contributor

Message from Gobot Gobot:

Patch Set 1: TryBot-Result-1

6 of 6 TryBots failed:
Failed on linux-amd64: https://storage.googleapis.com/go-build-log/500d79c4/linux-amd64_2d60c2a9.log
Failed on linux-386: https://storage.googleapis.com/go-build-log/500d79c4/linux-386_6784d523.log
Failed on freebsd-amd64-11_1: https://storage.googleapis.com/go-build-log/500d79c4/freebsd-amd64-11_1_891a49f3.log
Failed on openbsd-amd64-62: https://storage.googleapis.com/go-build-log/500d79c4/openbsd-amd64-62_a3597b40.log
Failed on windows-amd64-2016: https://storage.googleapis.com/go-build-log/500d79c4/windows-amd64-2016_4a1650bc.log
Failed on windows-386-2008: https://storage.googleapis.com/go-build-log/500d79c4/windows-386-2008_3b76a36b.log

Consult https://build.golang.org/ to see whether they are new failures.


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

@gopherbot
Copy link
Contributor

Message from Gerrit Bot:

Uploaded patch set 3: Commit message was updated.


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

CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843
@gopherbot
Copy link
Contributor

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

Please visit https://go-review.googlesource.com/#/c/crypto/+/110796 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link
Contributor

Message from Gerrit Bot:

Uploaded patch set 4: Commit message was updated.


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

@tmthrgd tmthrgd changed the title crypto/chacha20poly1305: correct AVX2 feature detection chacha20poly1305: correct AVX2 feature detection May 2, 2018
@gopherbot
Copy link
Contributor

Message from Gerrit Bot:

Uploaded patch set 5: Commit message was updated.


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

@gopherbot
Copy link
Contributor

Message from Tom Thorogood:

Patch Set 5:

(1 comment)

Sorry for my fighting with Gerritbot there.


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

@gopherbot
Copy link
Contributor

Message from Tobias Klauser:

Patch Set 5:

Patch Set 1:

Patch Set 1:

Build is still in progress...
This change failed on linux-amd64:
See https://storage.googleapis.com/go-build-log/500d79c4/linux-amd64_2d60c2a9.log

Consult https://build.golang.org/ to see whether it's a new failure. Other builds still in progress; subsequent failure notices suppressed until final report.

This is just golang/go#25199 right?

Yes, looks like it.


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

@gopherbot
Copy link
Contributor

Message from Tobias Klauser:

Patch Set 5: Code-Review+2

Patch Set 5:

(1 comment)

Sorry for my fighting with Gerritbot there.

No problem, thanks for the update.


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

gopherbot pushed a commit that referenced this pull request May 2, 2018
CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

Change-Id: I4719b8ff3211eb1c823099512e593e540d6f3be8
GitHub-Last-Rev: 70542b5
GitHub-Pull-Request: #44
Reviewed-on: https://go-review.googlesource.com/110796
Reviewed-by: Tobias Klauser <[email protected]>
@gopherbot
Copy link
Contributor

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

@gopherbot gopherbot closed this May 2, 2018
c-expert-zigbee pushed a commit to c-expert-zigbee/crypto_go that referenced this pull request Mar 28, 2022
CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

Change-Id: I4719b8ff3211eb1c823099512e593e540d6f3be8
GitHub-Last-Rev: 70542b53cd09fcae26c3579cd84bcee39a4b8a57
GitHub-Pull-Request: golang/crypto#44
Reviewed-on: https://go-review.googlesource.com/110796
Reviewed-by: Tobias Klauser <[email protected]>
c-expert-zigbee pushed a commit to c-expert-zigbee/crypto_go that referenced this pull request Mar 29, 2022
CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

Change-Id: I4719b8ff3211eb1c823099512e593e540d6f3be8
GitHub-Last-Rev: 70542b53cd09fcae26c3579cd84bcee39a4b8a57
GitHub-Pull-Request: golang/crypto#44
Reviewed-on: https://go-review.googlesource.com/110796
Reviewed-by: Tobias Klauser <[email protected]>
c-expert-zigbee pushed a commit to c-expert-zigbee/crypto_go that referenced this pull request Mar 29, 2022
CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

Change-Id: I4719b8ff3211eb1c823099512e593e540d6f3be8
GitHub-Last-Rev: 70542b53cd09fcae26c3579cd84bcee39a4b8a57
GitHub-Pull-Request: golang/crypto#44
Reviewed-on: https://go-review.googlesource.com/110796
Reviewed-by: Tobias Klauser <[email protected]>
LewiGoddard pushed a commit to LewiGoddard/crypto that referenced this pull request Feb 16, 2023
CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

Change-Id: I4719b8ff3211eb1c823099512e593e540d6f3be8
GitHub-Last-Rev: 70542b53cd09fcae26c3579cd84bcee39a4b8a57
GitHub-Pull-Request: golang/crypto#44
Reviewed-on: https://go-review.googlesource.com/110796
Reviewed-by: Tobias Klauser <[email protected]>
BiiChris pushed a commit to BiiChris/crypto that referenced this pull request Sep 15, 2023
CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

Change-Id: I4719b8ff3211eb1c823099512e593e540d6f3be8
GitHub-Last-Rev: 70542b5
GitHub-Pull-Request: golang#44
Reviewed-on: https://go-review.googlesource.com/110796
Reviewed-by: Tobias Klauser <[email protected]>
desdeel2d0m added a commit to desdeel2d0m/crypto that referenced this pull request Jul 1, 2024
CL 110355 switched out the adhoc cpu feature detection for x/sys/cpu, in
doing so the AVX2 check was broken. The assembly code uses MULX which is
part of BMI2.

Updates golang/go#24843

Change-Id: I4719b8ff3211eb1c823099512e593e540d6f3be8
GitHub-Last-Rev: 70542b53cd09fcae26c3579cd84bcee39a4b8a57
GitHub-Pull-Request: golang/crypto#44
Reviewed-on: https://go-review.googlesource.com/110796
Reviewed-by: Tobias Klauser <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants