[email protected] (Timo Buhrmester) writes: >The assembly code originates from >crypto/external/bsd/openssl/dist/crypto/sha/asm/sha1-x86_64.pl (around line >346), but seems to have been untouched for too long to be the culprit (a -head >build in March didn't provoke the problem yet).
Looks like the code has been recently activated without checking
that it works on a particular CPU.
--
--
Michael van Elst
Internet: [email protected]
"A potential Snark may lurk in every tree."
