---Reply to mail from Alexander R. Pruss about rotation
I just committed a faster version of rotatebitmap.c. Under PACE with
armlets disabled, on my NX, it shows a 100%+ speedup for 16bit rotation.
The armlet version generally shows about a 20% speedup.
I am curious how it performs on real
The best(?) I could try was 4 bit on my 16Mhz IIIx (and I had to
bypass the
fastEnough check). The old version was consistantly 0.03 seconds and the
new was 0.01 or 0.02 seconds. Quite a difference!!
(You could put in a for ( i = 0 ; i 50 ; i++ ) just before the call to
RotateBitmap() in
---Reply to mail from Alexander R. Pruss about rotation
From: Chris Hawks [EMAIL PROTECTED]
Lots more accurate. 23.61 sec as opposed to 28.25 sec. About a 16%
increase in speed.
Oh well, not much then.
What bit depth was that at? (The 1-bit was not optimized as heavily as the
8
From: Chris Hawks [EMAIL PROTECTED]
4 bit, best my IIIx can do.
4 bit rotation is currently rather inefficient. It could be significantly
improved if one split up the 4- and 2-bit rotation code into separate
routines. I'll send you a version that does that to see if it's worth the
extra
I just committed a faster version of rotatebitmap.c. Under PACE with
armlets disabled, on my NX, it shows a 100%+ speedup for 16bit rotation.
The armlet version generally shows about a 20% speedup.
I am curious how it performs on real 68K devices. I'd love to hear from
you. (Chris?)
Alex
On Fri, 25 Jul 2003, Chris Hawks wrote:
I updated my CVS code for the rotation stuff and all I get are
complaints about rotate.c and rotate.h missing!!
Did you forget something??
I forgot to issue cvs add commands. It's fixed now.
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL
Alex:
I updated my CVS code for the rotation stuff and all I get are
complaints about rotate.c and rotate.h missing!!
Did you forget something??
Christopher R. Hawks
HAWKSoft
-
Never attribute to conspiracy what can
Well, my next little Plucker project is a rotated view. I'm now adding
the UI and need to fix up some OS5 stuff. Unfortunately, OS5 blocks
access to the font data for the OS-supplied fonts, so on OS5 it will only
work with user-loaded font packages (another reason why we should have
them). My
