Date:	Mon, 9 Jul 2001 15:02:00 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	Gero Timann <gtimann AT nexgo DOT de>
Cc:	djgpp AT delorie DOT com
Subject:	Re: gcc 3.0 problem ?
In-Reply-To:	<1103_994419822@default>
Message-ID:	<Pine.A41.4.05.10107091501200.25696-100000@ieva06.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 6 Jul 2001, Gero Timann wrote:

> Hallo !
> 
> Some problems occur, if i recompile the allegro-lib with gcc 3.0. 
> Compile run's fine, but the resulting library doesn't work, if it's compiled 
> with optimation-flag -O2 or -O3. Ok, allegro is very a complicate near
> hardware programmed library, but, strange, -O1 and -O2/-O3 with 
> generating debugging code (=-g) works (strange !?). Never seen
> this with gcc 2.95.3, therefore it's maybe a gcc3.0-problem.
> 

Known problem

Remove -fomit-frame-pointer from compiler options

Andris

- Raw text -