summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/crypto
diff options
context:
space:
mode:
authormiod <>2014-05-02 19:59:16 +0000
committermiod <>2014-05-02 19:59:16 +0000
commit9b91067767652b8b5119230a0a75c4b09267511d (patch)
treeb001363f34bc734a46d4080316ad1c0574f515a3 /src/lib/libcrypto/crypto
parenta928011ef8b6701a9f677f7a5f330726c9b7cc2f (diff)
downloadopenbsd-9b91067767652b8b5119230a0a75c4b09267511d.tar.gz
openbsd-9b91067767652b8b5119230a0a75c4b09267511d.tar.bz2
openbsd-9b91067767652b8b5119230a0a75c4b09267511d.zip
The assembly sha512 code detects at runtime if it is running on a 64-bit
processor (PA2.0) and, if so, switches to 64-bit code. However, when running under a 32-bit OpenBSD/hppa kernel, there is no guarantee that the upper part of the registers will be preserved accross context switches (or even userland->kernel boundaries), which causes this code to fail. Wrap the generated code within #ifndef __OpenBSD__ in that case, to avoid using the 64-bit code completely. (OpenBSD/hppa64, once stable, will not be affected by this)
Diffstat (limited to 'src/lib/libcrypto/crypto')
0 files changed, 0 insertions, 0 deletions