Date:	Fri, 22 Mar 1996 13:51:49 +0800 (GMT+0800)
From:	"Orlando A. Andico" <orly AT natalie DOT eee DOT upd DOT edu DOT ph>
To:	"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
cc:	DJGPP AT delorie DOT com
Subject:	Re: When and how does longjmp() `clobber' variables?
In-Reply-To:	<A8BE871245@fs2.mt.umist.ac.uk>
Message-ID:	<Pine.LNX.3.91.960322134950.245A-100000@natalie.eee.upd.edu.ph>
MIME-Version:	1.0

On Thu, 21 Mar 1996, A.Appleyard wrote:

> I have a big Gnu C++ program (an Emacs-type text editor) in several files,
> which I compile with `gcc <filename> -c -g -Wall', getting no fault remarks or
> cautions or warnings. But today I compiled it with `gcc <filename> -c -g -O3',
> and got a mass of warnings of this type:-
<snip>

I had a similar program a while back with a Basic interpreter using -O2 
instead of -O. I think it's because at the higher levels of optimization 
the compiler inlines everything in sight and this can cause weird 
problems. As for the vfork(), I suppose you can ignore it because vfork() 
is "implemented" to fail under DJGPP.

                                             ------------------------
                                              Orlando A. Andico
                                              oandico AT eee DOT upd DOT edu DOT ph
                                             ------------------------

- Raw text -