From:	"Guido Bursch" <bursch AT uni-muenster DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	what is __djgpp_exception_processor??
Date:	Sat, 12 Apr 1997 19:33:01 +0200
Organization:	Westfaelische Wilhelms-Universitaet Muenster, Germany
Lines:	30
Sender:	"Guido Bursch" <bursch AT uni-muenster DOT de>
Message-ID:	<Pine.A41.3.96.970412191602.124522A-100000@asterix.uni-muenster.de>
NNTP-Posting-Host:	asterix.uni-muenster.de
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Hi all!

I just ported my little vectorcube program from Turbo c
to djgpp2. It took me about 2 hours for a 400 lines sourcecode
(speaks for the quality of djgpp) without asm-optimizing.
The result was a bit disappointing: it ran 4 times slower than with
Turbo c which is surely my fault and not the of djgpp.
gprof reported me that 72% (22% self) of the runtime were wasted by
the function (or macro or whatever) "__djgpp_exception_processor"
without giving me the number of calls to it.
To my program is to say that FP- operations are heavyly used and I 
have to use an FP- emulator because I dont't own an 387 FPU.
2 times I call an interrupt (set vga/text) , use 
1* __djgpp_nearptr_enable() + disable, clear the virtual screen with
memset (400 times), copy it to vga - memory mith memcpy (400 times) and draw
hlines with memset (44606 times).
My question is now, which function may use "__djgpp_exception_processor"
and how can I do the things without or with less use of it,
and btw what is it ?

I would be very happy, if someone could give me an answer to my
question but please don't personally email me (we have problems with our
mail_server).


                                   Thank you all

- Raw text -