Google Git
Sign in
go / crypto / c7dcf104e3a7a1417abc0230cb0d5240d764159d
commitc7dcf104e3a7a1417abc0230cb0d5240d764159d[log] [tgz]
authorIlya Tocar <ilya.tocar@intel.com>Thu Mar 01 11:15:02 2018 -0600
committerIlya Tocar <ilya.tocar@intel.com>Thu Mar 08 18:56:24 2018 +0000
treeaefec40f01cf5dc42fab0dd20fbc309fd9671b72
parent7effd64e1180aa386cd36da9ca55a1e9fc7cf7cb [diff]
ripemd160: use bits.Rotate for rotates

Replace x << k | x >> (32 - k) with bits.RotateLeft32 and add
benchmark to check performance. This makes code cleaner and improves performance:

MillionA-6  34.8ms ± 1%  26.7ms ± 1%  -23.41%  (p=0.000 n=10+10)

Change-Id: I1b0c45f5ea12c7b53ab1ec5a26efc1903555fa66
Reviewed-on: https://go-review.googlesource.com/97915
Run-TryBot: Ilya Tocar <ilya.tocar@intel.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2 files changed
tree: aefec40f01cf5dc42fab0dd20fbc309fd9671b72
  1. acme/
  2. argon2/
  3. bcrypt/
  4. blake2b/
  5. blake2s/
  6. blowfish/
  7. bn256/
  8. cast5/
  9. chacha20poly1305/
  10. cryptobyte/
  11. curve25519/
  12. ed25519/
  13. hkdf/
  14. internal/
  15. md4/
  16. nacl/
  17. ocsp/
  18. openpgp/
  19. otr/
  20. pbkdf2/
  21. pkcs12/
  22. poly1305/
  23. ripemd160/
  24. salsa20/
  25. scrypt/
  26. sha3/
  27. ssh/
  28. tea/
  29. twofish/
  30. xtea/
  31. xts/
  32. .gitattributes
  33. .gitignore
  34. AUTHORS
  35. codereview.cfg
  36. CONTRIBUTING.md
  37. CONTRIBUTORS
  38. LICENSE
  39. PATENTS
  40. README.md
README.md

Go Cryptography

This repository holds supplementary Go cryptography libraries.

Download/Install

The easiest way to install is to run go get -u golang.org/x/crypto/.... You can also manually git clone the repository to $GOPATH/src/golang.org/x/crypto.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the crypto repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/crypto:” in the subject line, so it is easy to find.

Note that contributions to the cryptography package receive additional scrutiny due to their sensitive nature. Patches may take longer than normal to receive feedback.