From: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: 32bit memcpy function? _NEW_ Tried FPU memcpy (problem with CWSDPMI)
Date: 30 Nov 1997 08:31:03 GMT
Organization: The National Capital FreeNet
Lines: 24
Message-ID: <65r887$fr9@freenet-news.carleton.ca>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 971123153118 DOT 19570a-100000 AT is> <34791FD2 DOT DC541BF1 AT linux DOT dpilink DOT com> <Pine DOT ULT DOT 3 DOT 95 DOT 971127181022 DOT 831A-100000 AT dec5 DOT vse DOT cz>
Reply-To: ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host: freenet5.carleton.ca
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk


Michal Mertl (xmerm05 AT manes DOT vse DOT cz) writes:
> On Sun, 23 Nov 1997, Speed wrote:
> 
>> So it is equivalent to a 'rep movsl'? (assuming, of course, the source,
>> dest, and count are already set)
>> 
> Yes, it is. Why you don't just look at the output. There are at least 3 good
> debuggers for DJGPP.
> 
> Other thing is that I tried to write memcpy using 64bit FPU registers as
> someone here suggested. It's about _20% faster_!!
> 
> __here is the source code of memcpyfpu.c __

NICE... anyone want to consider replacing the default memcpy with this
feller? (Of course, to avoid it running 50000% SLOWER on FPU-less machines
you might want to make the regular one be used instead if the FPU isn't
found. :-))
--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh