Message-Id: <199903270452.XAA26034@indy1.indy.net>
From: "Steve Snyder" <ssnyder AT indy DOT net>
To: "pgcc AT delorie DOT com" <pgcc AT delorie DOT com>
Date: Fri, 26 Mar 1999 23:51:00 -0500 (EST)
X-Mailer: PMMail 2.00.1500 for OS/2 Warp 4.00
In-Reply-To: <36F96937.8A182EE7@lycosmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: EGCS Optimizations break ZLIB 1.1.3
Reply-To: pgcc AT delorie DOT com
X-Mailing-List: pgcc AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

http://www.gcc.ml.org/pgcc-faq.html#opts

Another switch to keep in mind is -fno-risc-const.


On Wed, 24 Mar 1999 17:37:43 -0500, Adam Schrotenboer wrote:
>Why is -fno-risc not doc'd in the GCC info file??? I can't find it.
>
>And thank you, it worked.
>
>Ronald de Man wrote:
>
>> On Wed, Mar 24, 1999 at 10:46:51AM -0500, ADAM SCHROTENBOER wrote:
>> > When I build zlib 1.1.3 w/ optimzations set to 3 or higher, it breaks zlib.
>> >
>> > The example program crashes w/ a SIGSEGV in __djmove_data+37
>> >
>> > I don't have the full stack trace here, but I do have it at home.
>> >
>> > With 06, the stack trace has 2 entries, w/ 03, it has something like 6, but
>> > both GPF in the same function.
>>
>> I remember zlib failing with pgcc (might have been 1.0.2) and -O6.
>> Adding -fno-risc worked for me. That was probably with older versions
>> of both zlib and pgcc than you are using, but you might give '-O6 -fno-risc'
>> a try.
>>
>> Ronald
>
>
>

*** Steve Snyder ***