summaryrefslogtreecommitdiff
path: root/mpn
diff options
context:
space:
mode:
authorKevin Ryde <user42@zip.com.au>2001-04-03 01:34:21 +0200
committerKevin Ryde <user42@zip.com.au>2001-04-03 01:34:21 +0200
commit3cd56ecf42d0faa84f90eaa74e59aa508eacc920 (patch)
tree3bb9708284aa674c4601a50bedfa730e2da4f1a6 /mpn
parentebbc65ee71b8e41f56e959833b4f04b71fb6f69f (diff)
downloadgmp-3cd56ecf42d0faa84f90eaa74e59aa508eacc920.tar.gz
Reword a comment.
Diffstat (limited to 'mpn')
-rw-r--r--mpn/x86/pentium/mmx/mul_1.asm15
1 files changed, 6 insertions, 9 deletions
diff --git a/mpn/x86/pentium/mmx/mul_1.asm b/mpn/x86/pentium/mmx/mul_1.asm
index 0005f7ac3..18c214490 100644
--- a/mpn/x86/pentium/mmx/mul_1.asm
+++ b/mpn/x86/pentium/mmx/mul_1.asm
@@ -29,15 +29,12 @@ include(`../config.m4')
C mp_limb_t mpn_mul_1 (mp_ptr dst, mp_srcptr src, mp_size_t size,
C mp_limb_t multiplier);
C
-C When the multiplier is 16 bits some special case MMX code is used. This
-C isn't a particularly important in general, but small multipliers might
-C come about reasonably often from mpz_mul_ui etc.
-C
-C In the MMX code, if the size is odd there's roughly a 5 cycle penalty, so
-C times for say size==7 and size==8 end up being quite close. If src isn't
-C aligned to an 8 byte boundary then one limb is processed separately with
-C roughly a 5 cycle penalty, so in that case it's say size==8 and size==9
-C which are close.
+C When the multiplier is 16 bits some special case MMX code is used. Small
+C multipliers might arise reasonably often from mpz_mul_ui etc. If the size
+C is odd there's roughly a 5 cycle penalty, so times for say size==7 and
+C size==8 end up being quite close. If src isn't aligned to an 8 byte
+C boundary then one limb is processed separately with roughly a 5 cycle
+C penalty, so in that case it's say size==8 and size==9 which are close.
C
C Alternatives:
C