Date: Sun, 21 May 2000 08:16:46 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Thomas J. Hruska" <shinelight AT crosswinds DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Inline ASM question...
In-Reply-To: <3.0.6.32.20000520173229.007b4d20@pop.crosswinds.net>
Message-ID: <Pine.SUN.3.91.1000521081335.15757D-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 Sat, 20 May 2000, Thomas J. Hruska wrote:

> At 04:37 PM 5/20/00 -0400, you wrote:
> >Library function `movedata' already does that.  I suggest to use it
> >instead of messing with inline assembly.
> 
> Hmm...fps doesn't change very much even with _movedatal.

Then maybe moving data is not your problem at all.

> BIOS video calls for bank switching are my problem then.  Ho hum.

I suggest to profile your program instead of guessing.  DJGPP toolchain 
includes a profiler, see chapter 13 of the FAQ for details.  Usually,
the results of profiling surprise programmers, which means that guessing 
the hot spots doesn't work very well ;-).

If the profile shows that moving data takes a significant portion of the 
run time, then it could be that your VGA is simply too slow for the 
particular algorithm you've chosen to implement.