X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Date:	Mon, 28 May 2012 23:50:22 +0300
From:	Eli Zaretskii <eliz AT gnu DOT org>
Subject:	Re: gprof output
In-reply-to:	<e9a9d1fc-4410-425e-9b22-74529940d0b8@eh4g2000vbb.googlegroups.com>
X-012-Sender:	halo1 AT inter DOT net DOT il
To:	djgpp AT delorie DOT com
Message-id:	<83aa0s114h.fsf@gnu.org>
References:	<7822bb4a-1059-491a-8489-e1d9f3dbc501 AT l17g2000vbj DOT googlegroups DOT com> <a2en0pFpq6U1 AT mid DOT dfncis DOT de> <e9a9d1fc-4410-425e-9b22-74529940d0b8 AT eh4g2000vbb DOT googlegroups DOT com>
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

> From: Georg <dosusb AT googlemail DOT com>
> Date: Mon, 28 May 2012 13:37:54 -0700 (PDT)
> 
> I now removed my _dpmi_int calls from my program but still 80-90% of
> the processing time is done for _dpmi_int. Does djgpp call this
> internally?

Yes.

> I use int86() to query the mouse and getch() plus bioskey() to query
> the keyboard. Could these functions cause this?

Of course!  Any real-mode interrupt call goes through __dpmi_int,
because that's the _only_ way to invoke real-mode DOS/BIOS services
from protected mode.

I'm quite sure this is in the FAQ.

- Raw text -