Xref: news2.mv.net comp.os.msdos.djgpp:7692
From: Elliott Oti <e DOT oti AT stud DOT warande DOT ruu DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: -fomit-frame-pointer dangers: FIRE!
Date: Tue, 20 Aug 1996 11:41:57 -0700
Organization: Academic Computer Centre Utrecht, (ACCU)
Lines: 20
Message-ID: <321A06F5.40E8@stud.warande.ruu.nl>
References: <Pine DOT NEB DOT 3 DOT 95 DOT 960816133628 DOT 4971A-100000 AT ananke DOT amu DOT edu DOT pl>
NNTP-Posting-Host: warande1078.warande.ruu.nl
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Mark Habersack wrote:
> 
> On Tue, 13 Aug 1996, Elliott Oti wrote:
> 
> >Compiling with -ffast-math , -fomit-frame-pointer reduces
>                               ^^^^^speaking of this one. I read that this
> switch causes WinXX to break down??? Well, I use it all the time and so far no
> failures!! So have anyone of you had any problems of this nature with the
> switch? And if so, in what environment (I checked Win3.11, Win95 & WinNT -
> everything's OK)
> 

info says that using -fomit-frame-pointer prevents debugging on i386 machines
(never tried it meself), but I find Mark's question an interesting one.
I try to make my programs as Win-friendly as possible, and they crash
fairly often ( sound routines especially playing mods are the worst
culprits), but the switch has little to do with it. I now use it all
the time, as the extra register makes ALL the difference. Still -- where there's
smoke, there's fire . Only, where's the fire? Any of you guys seen fire?
Any ideas, Eli?