{"schema":"libjg2-1", "vpath":"/git/", "avatar":"/git/avatar/", "alang":"", "gen_ut":1753258751, "reponame":"openssl", "desc":"OpenSSL", "owner": { "name": "Andy Green", "email": "andy@warmcat.com", "md5": "c50933ca2aa61e0fe2c43d46bb6b59cb" },"url":"https://warmcat.com/repo/openssl", "f":3, "items": [ {"schema":"libjg2-1", "cid":"61a65dbdeb31e0e29b4f2308a3bde775", "commit": {"type":"commit", "time": 1480091668, "time_ofs": 60, "oid_tree": { "oid": "d54e025fd23c8e601a3a56c47763c1ba6bf416c2", "alias": []}, "oid":{ "oid": "5ae5dc96610f0a598dac9d2f267b5c0ddd77b2e4", "alias": []}, "msg": "INSTALL: clarify 386 and no-sse2 options.", "sig_commit": { "git_time": { "time": 1480091668, "offset": 60 }, "name": "Andy Polyakov", "email": "appro@openssl.org", "md5": "50bd64fa2a792cbbf679fa16213a3b2a" }, "sig_author": { "git_time": { "time": 1479675161, "offset": 60 }, "name": "Andy Polyakov", "email": "appro@openssl.org", "md5": "50bd64fa2a792cbbf679fa16213a3b2a" }}, "body": "INSTALL: clarify 386 and no-sse2 options.\n\nReviewed-by: Rich Salz \u003crsalz@openssl.org\u003e\nReviewed-by: Richard Levitte \u003clevitte@openssl.org\u003e\n" , "diff": "diff --git a/Configure b/Configure\nindex 2bdf87b..c005781 100755\n--- a/Configure\n+++ b/Configure\n@@ -60,11 +60,12 @@ my $usage\u003d\u0022Usage: Configure [no-\u003ccipher\u003e ...] [enable-\u003ccipher\u003e ...] [-Dxxx] [-lx\n # zlib-dynamic\tLike \u0022zlib\u0022, but the zlib library is expected to be a shared\n #\t\tlibrary and will be loaded in run-time by the OpenSSL library.\n # sctp include SCTP support\n-# 386 generate 80386 code\n # enable-weak-ssl-ciphers\n # Enable weak ciphers that are disabled by default. This currently\n # only includes RC4 based ciphers.\n-# no-sse2\tdisables IA-32 SSE2 code, above option implies no-sse2\n+# 386 generate 80386 code in assembly modules\n+# no-sse2 disables IA-32 SSE2 code in assembly modules, the above\n+# mentioned '386' option implies this one\n # no-\u003ccipher\u003e build without specified algorithm (rsa, idea, rc5, ...)\n # -\u003cxxx\u003e +\u003cxxx\u003e compiler options are passed through\n # -static while -static is also a pass-through compiler option (and\ndiff --git a/INSTALL b/INSTALL\nindex 2007148..fa50091 100644\n--- a/INSTALL\n+++ b/INSTALL\n@@ -383,19 +383,19 @@\n Don't build SRTP support\n \n no-sse2\n- Exclude SSE2 code paths. Normally SSE2 extension is\n- detected at run-time, but the decision whether or not the\n- machine code will be executed is taken solely on CPU\n- capability vector. This means that if you happen to run OS\n- kernel which does not support SSE2 extension on Intel P4\n- processor, then your application might be exposed to\n- \u0022illegal instruction\u0022 exception. There might be a way\n- to enable support in kernel, e.g. FreeBSD kernel can be\n- compiled with CPU_ENABLE_SSE, and there is a way to\n- disengage SSE2 code paths upon application start-up,\n- but if you aim for wider \u0022audience\u0022 running such kernel,\n- consider no-sse2. Both the 386 and no-asm options imply\n- no-sse2.\n+ Exclude SSE2 code paths from 32-bit x86 assembly modules.\n+ Normally SSE2 extension is detected at run-time, but the\n+ decision whether or not the machine code will be executed\n+ is taken solely on CPU capability vector. This means that\n+ if you happen to run OS kernel which does not support SSE2\n+ extension on Intel P4 processor, then your application\n+ might be exposed to \u0022illegal instruction\u0022 exception.\n+ There might be a way to enable support in kernel, e.g.\n+ FreeBSD kernel can be compiled with CPU_ENABLE_SSE, and\n+ there is a way to disengage SSE2 code paths upon application\n+ start-up, but if you aim for wider \u0022audience\u0022 running\n+ such kernel, consider no-sse2. Both the 386 and\n+ no-asm options imply no-sse2.\n \n enable-ssl-trace\n Build with the SSL Trace capabilities (adds the \u0022-trace\u0022\n@@ -458,11 +458,12 @@\n where loading of shared libraries is supported.\n \n 386\n- On Intel hardware, use the 80386 instruction set only\n- (the default x86 code is more efficient, but requires at\n- least a 486). Note: Use compiler flags for any other CPU\n- specific configuration, e.g. \u0022-m32\u0022 to build x86 code on\n- an x64 system.\n+ In 32-bit x86 builds, when generating assembly modules,\n+ use the 80386 instruction set only (the default x86 code\n+ is more efficient, but requires at least a 486). Note:\n+ This doesn't affect code generated by compiler, you're\n+ likely to complement configuration command line with\n+ suitable compiler-specific option.\n \n enable-tls1_3\n TODO(TLS1.3): Make this enabled by default\n@@ -500,7 +501,12 @@\n These system specific options will be passed through to the\n compiler to allow you to define preprocessor symbols, specify\n additional libraries, library directories or other compiler\n- options.\n+ options. It might be worth noting that some compilers\n+ generate code specifically for processor the compiler\n+ currently executes on. This is not necessarily what you might\n+ have in mind, since it might be unsuitable for execution on\n+ other, typically older, processor. Consult your compiler\n+ documentation.\n \n \n Installation in Detail\n","s":{"c":1753258751,"u": 16087}} ],"g": 17896,"chitpc": 0,"ehitpc": 0,"indexed":0 , "ab": 0, "si": 0, "db":0, "di":0, "sat":0, "lfc": "0000"}