http://repzret.org/p/repzret/

My read of this:  Long time ago (Think Conan, not dinasaurs) during the race
to make speedier processors, a cpu vendor built a pipeline with a bad stall,
and proposed a tremendously hasky workaround.  A wizard adopted this into his
perl scroll, and failed to reflect later when no compiler adopted the practice.
This relic remains at the tail end of some functions in OpenSSL as
".byte 0xf3,0xc3".  Banish it straight to hell.
ok mlarkin, others also stared blankly

1 files changed, 5 insertions, 5 deletions

diff --git a/src/lib/libcrypto/aes/asm/aes-x86_64.pl b/src/lib/libcrypto/aes/asm/aes-x86_64.pl
index c37fd55648..9072f603a9 100755
--- a/src/lib/libcrypto/aes/asm/aes-x86_64.pl
+++ b/src/lib/libcrypto/aes/asm/aes-x86_64.pl
@@ -352,7 +352,7 @@ ___
 ___
         }
 $code.=<<___;
-        .byte   0xf3,0xc3                       # rep ret
+        retq
 .size   _x86_64_AES_encrypt,.-_x86_64_AES_encrypt
 ___
 
@@ -580,7 +580,7 @@ $code.=<<___;
         xor     4($key),$s1
         xor     8($key),$s2
         xor     12($key),$s3
-        .byte   0xf3,0xc3                       # rep ret
+        retq
 .size   _x86_64_AES_encrypt_compact,.-_x86_64_AES_encrypt_compact
 ___
 
@@ -925,7 +925,7 @@ ___
 ___
         }
 $code.=<<___;
-        .byte   0xf3,0xc3                       # rep ret
+        retq
 .size   _x86_64_AES_decrypt,.-_x86_64_AES_decrypt
 ___
 
@@ -1179,7 +1179,7 @@ $code.=<<___;
         xor     4($key),$s1
         xor     8($key),$s2
         xor     12($key),$s3
-        .byte   0xf3,0xc3                       # rep ret
+        retq
 .size   _x86_64_AES_decrypt_compact,.-_x86_64_AES_decrypt_compact
 ___
 
@@ -1496,7 +1496,7 @@ $code.=<<___;
 .Lbadpointer:
         mov     \$-1,%rax
 .Lexit:
-        .byte   0xf3,0xc3                       # rep ret
+        retq
 .size   _x86_64_AES_set_encrypt_key,.-_x86_64_AES_set_encrypt_key
 ___