diff options
| author | Andy Polyakov <appro@openssl.org> | 2005-05-31 12:39:54 +0000 |
|---|---|---|
| committer | Andy Polyakov <appro@openssl.org> | 2005-05-31 12:39:54 +0000 |
| commit | db6b4e379144d8f8d9db3477e36b90d4fd23a36e (patch) | |
| tree | 4787635d024999ca6ab78ee9e3831f7f0758fe0e /PROBLEMS | |
| parent | 20a85e9f69b6eed758667d59a718190ff43c11b8 (diff) | |
Mention more GCC bugs in ./PROBLEMS.
Diffstat (limited to 'PROBLEMS')
| -rw-r--r-- | PROBLEMS | 28 |
1 files changed, 21 insertions, 7 deletions
@@ -48,20 +48,34 @@ 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 -triggered by some of the code in OpenSSL, more specifically in -PEM_get_EVP_CIPHER_INFO(). The triggering code is the following: +- 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: header+=11; if (*header != '4') return(0); header++; if (*header != ',') return(0); header++; -What happens is that gcc might optimize a little too agressively, and -you end up with an extra incrementation when *header != '4'. + What happens is that gcc might optimize a little too agressively, and + 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. + 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. |