Date: Mon, 18 Jun 2001 10:14:15 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: April <awhite AT mail DOT rosecom DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: [Fwd: Re: gprof question]
In-Reply-To: <3B2D40BE.4A613509@mail.rosecom.ca>
Message-ID: <Pine.SUN.3.91.1010618101358.22931P-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Sun, 17 Jun 2001, April wrote:

> > Anything that does an OS call [causes a __dpmi_int] - read, time,
> > sbrk (used by malloc), sometimes getkey().
> 
> Would all file opening - fopen / open / _dos_open / _open - and
> corresponding i/o functions generate the same type of OS call?

Yes.  Any function which eventually calls DOS or BIOS will go through
__dpmi_int and __dj_movedata.

> What I'm asking is: if I don't use _open and _read, would the
> interrupt calls be reduced?

Yes.  But can your program really run without reading those files?  If
it can, why do you call _open and _read in the first place?