Date: Mon, 9 Jul 2001 16:44:32 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: Gero Timann <gtimann AT nexgo DOT de>, djgpp AT delorie DOT com
Subject: Re: gcc 3.0 problem ?
In-Reply-To: <Pine.A41.4.05.10107091501200.25696-100000@ieva06.lanet.lv>
Message-ID: <Pine.SUN.3.91.1010709164315.8678C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Mon, 9 Jul 2001, Andris Pavenis wrote:

> > 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

Is this a bug?  I know that -fomit-frame-pointer makes debugging hard or 
impossible, but the OP seems to say that the library doesn't work, not 
just cannot be debug.