Conversion to UTF-8 where needed

[openssl.git] / crypto / sha / asm / sha1-586.pl

diff --git a/crypto/sha/asm/sha1-586.pl b/crypto/sha/asm/sha1-586.pl
index 8377299b1e3383f68896d53b69993fc0a3a1e31c..e0b5d83b62018a86a0204b230a56197afcda4e21 100644 (file)
--- a/crypto/sha/asm/sha1-586.pl
+++ b/crypto/sha/asm/sha1-586.pl
@@ -66,9 +66,9 @@
 # switch to AVX alone improves performance by as little as 4% in
 # comparison to SSSE3 code path. But below result doesn't look like
 # 4% improvement... Trouble is that Sandy Bridge decodes 'ro[rl]' as
-# pair of µ-ops, and it's the additional µ-ops, two per round, that
+# pair of µ-ops, and it's the additional µ-ops, two per round, that
 # make it run slower than Core2 and Westmere. But 'sh[rl]d' is decoded
-# as single µ-op by Sandy Bridge and it's replacing 'ro[rl]' with
+# as single µ-op by Sandy Bridge and it's replacing 'ro[rl]' with
 # equivalent 'sh[rl]d' that is responsible for the impressive 5.1
 # cycles per processed byte. But 'sh[rl]d' is not something that used
 # to be fast, nor does it appear to be fast in upcoming Bulldozer
@@ -450,7 +450,7 @@ sub sha1msg2        { sha1op38(0xca,@_); }
        &sub    ("esp",32);
 
        &movdqu ($ABCD,&QWP(0,$ctx));
-       &movd   ($E,&QWP(16,$ctx));
+       &movd   ($E,&DWP(16,$ctx));
        &and    ("esp",-32);
        &movdqa ($BSWAP,&QWP(0x50,$tmp1));      # byte-n-word swap