From 739b09b33140a7cde6da09372fc371d59f4751c7 Mon Sep 17 00:00:00 2001
From: deraadt <>
Date: Mon, 11 Dec 2017 05:48:01 +0000
Subject: 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

---
 src/lib/libcrypto/perlasm/x86_64-xlate.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/lib/libcrypto/perlasm')

diff --git a/src/lib/libcrypto/perlasm/x86_64-xlate.pl b/src/lib/libcrypto/perlasm/x86_64-xlate.pl
index a8393d2730..5f7f585549 100755
--- a/src/lib/libcrypto/perlasm/x86_64-xlate.pl
+++ b/src/lib/libcrypto/perlasm/x86_64-xlate.pl
@@ -149,7 +149,7 @@ my %globals;
 		    $epilogue = "movq	8(%rsp),%rdi\n\t" .
 				"movq	16(%rsp),%rsi\n\t";
 		}
-	    	$epilogue . ".byte	0xf3,0xc3";
+	    	$epilogue . "retq";
 	    } elsif ($self->{op} eq "call" && !$elf && $current_segment eq ".init") {
 		".p2align\t3\n\t.quad";
 	    } else {
-- 
cgit v1.2.3-55-g6feb