diff options
author | Andy Polyakov <appro@openssl.org> | 2005-02-06 13:10:23 +0000 |
---|---|---|
committer | Andy Polyakov <appro@openssl.org> | 2005-02-06 13:10:23 +0000 |
commit | 216ddfaf6bfc775b68c04d3666dd0b555296000b (patch) | |
tree | 1ac0924dce722a3858eb8d75f6a5b6582cb4df3d /INSTALL | |
parent | 8aa36bcac9b75f5f85048e2359ccfd44383d178c (diff) | |
download | openssl-new-216ddfaf6bfc775b68c04d3666dd0b555296000b.tar.gz |
Mention no-sse2 option in INSTALL note.
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -77,6 +77,20 @@ 386 Use the 80386 instruction set only (the default x86 code is more efficient, but requires at least a 486). + no-sse2 Exclude SSE2 code pathes. Normally SSE2 extention is + detected at run-time, but the decision whether or not the + machine code will be executed is taken solely on CPU + capability vector. This means that if you happen to run OS + kernel which does not support SSE2 extension on Intel P4 + processor, then your application might be exposed to + "illegal instruction" exception. There might be a way + to enable support in kernel, e.g. FreeBSD kernel can be + compiled with CPU_ENABLE_SSE, and there is a way to + disengage SSE2 code pathes upon application start-up, + but if you aim for wider "audience" running such kernel, + consider no-sse2. Both 386 and no-asm options above imply + no-sse2. + no-<cipher> Build without the specified cipher (bf, cast, des, dh, dsa, hmac, md2, md5, mdc2, rc2, rc4, rc5, rsa, sha). The crypto/<cipher> directory can be removed after running |