Loading PROBLEMS +21 −7 Original line number Diff line number Diff line Loading @@ -48,9 +48,9 @@ will interfere with each other and lead to test failure. The solution is simple for now: don't run parallell make when testing. * Bugs in gcc 3.0 triggered * Bugs in gcc triggered According to a problem report, there are bugs in gcc 3.0 that are - According to a problem report, there are bugs in gcc 3.0 that are triggered by some of the code in OpenSSL, more specifically in PEM_get_EVP_CIPHER_INFO(). The triggering code is the following: Loading @@ -63,6 +63,20 @@ you end up with an extra incrementation when *header != '4'. We recommend that you upgrade gcc to as high a 3.x version as you can. - According to multiple problem reports, some of our message digest implementations trigger bug[s] in code optimizer in gcc 3.3 for sparc64 and gcc 2.96 for ppc. Former fails to complete RIPEMD160 test, while latter - SHA one. The recomendation is to upgrade your compiler. This naturally applies to other similar cases. - There is a subtle Solaris x86-specific gcc run-time environment bug, which "falls between" OpenSSL [0.9.8 and later], Solaris ld and GCC. The bug manifests itself as Segmentation Fault upon early application start-up. The problem can be worked around by patching the environment according to http://www.openssl.org/~appro/values.c. * solaris64-sparcv9-cc SHA-1 performance with WorkShop 6 compiler. As subject suggests SHA-1 might perform poorly (4 times slower) Loading Loading
PROBLEMS +21 −7 Original line number Diff line number Diff line Loading @@ -48,9 +48,9 @@ will interfere with each other and lead to test failure. The solution is simple for now: don't run parallell make when testing. * Bugs in gcc 3.0 triggered * Bugs in gcc triggered According to a problem report, there are bugs in gcc 3.0 that are - According to a problem report, there are bugs in gcc 3.0 that are triggered by some of the code in OpenSSL, more specifically in PEM_get_EVP_CIPHER_INFO(). The triggering code is the following: Loading @@ -63,6 +63,20 @@ you end up with an extra incrementation when *header != '4'. We recommend that you upgrade gcc to as high a 3.x version as you can. - According to multiple problem reports, some of our message digest implementations trigger bug[s] in code optimizer in gcc 3.3 for sparc64 and gcc 2.96 for ppc. Former fails to complete RIPEMD160 test, while latter - SHA one. The recomendation is to upgrade your compiler. This naturally applies to other similar cases. - There is a subtle Solaris x86-specific gcc run-time environment bug, which "falls between" OpenSSL [0.9.8 and later], Solaris ld and GCC. The bug manifests itself as Segmentation Fault upon early application start-up. The problem can be worked around by patching the environment according to http://www.openssl.org/~appro/values.c. * solaris64-sparcv9-cc SHA-1 performance with WorkShop 6 compiler. As subject suggests SHA-1 might perform poorly (4 times slower) Loading
