Xref:	news-dnh.mv.net comp.os.msdos.djgpp:2604
Path:	news-dnh.mv.net!mv!news.sprintlink.net!news.bluesky.net!solaris.cc.vt.edu!newsfeed.internetmci.com!news.msfc.nasa.gov!elroy.jpl.nasa.gov!decwrl!waikato!comp.vuw.ac.nz!tao.sans.vuw.ac.nz!empty
From:	empty AT sans DOT vuw DOT ac DOT nz (Malcolm Taylor)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Missing interrupts???
Date:	13 Oct 1995 00:12:10 GMT
Organization:	SANS, Student Access Network System
Lines:	23
References:	<45f3l6$in5 AT nic-nac DOT CSU DOT net> <45gm42$rnj AT newsbf02 DOT news DOT aol DOT com>
Nntp-Posting-Host:	tao.sans.vuw.ac.nz
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

Hardgeus (hardgeus AT aol DOT com) wrote:

: Funny thing...I had the same problem...however what I did about it 
: probably won't be of any help.  I compiled it without optimization.
: I still don't know why it didn't work before, but I'm not going to 
: complain.

The optimizer under -O3 optimization will take code not specifically 
called inline and inline it. It will also reorder instruction to gain 
better speed. To stop this from happening call any functions (or 
assembly) that you don't want inlined __volitile__ and this will stop the 
compiler from inlining it. Otherwise using -O2 or -O1 will not do this. 
Also compiling without optimizations at all will not inline any code 
(even code specified as inline or __inline__).
If you want to know more about the optimizer (always a good thing) then 
read the gcc info files.

Hope this helps

Malcolm

: John R. McCawley III
: Cap'n Hardgeus

- Raw text -