From: Richard Levitte <levitte@openssl.org>
Date: Wed, 4 Dec 2002 08:24:18 +0000 (+0000)
Subject: A gcc 3.0 bug is triggered by our code.  Add a section about it in PROBLEMS.
X-Git-Tag: STATE_before_zlib~28
X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff_plain;h=ff3345cb721dcbea19edd6e2d663490c1c721e67

A gcc 3.0 bug is triggered by our code.  Add a section about it in PROBLEMS.
PR: 375
---

diff --git a/PROBLEMS b/PROBLEMS
index bf532d112b..56bc73816b 100644
--- a/PROBLEMS
+++ b/PROBLEMS
@@ -46,3 +46,19 @@ scripts use the same name for output and input files, which means different
 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
+
+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'.
+
+We recommend that you upgrade gcc to as high a 3.x version as you can.