Ok, there was a need for OPENSSL_cleanse() instead of bzero() to prevent

supposedly smart compilers from optimizing memory cleanups away. Understood.

Ok, in case of an hypothetically super smart compiler, OPENSSL_cleanse() had
to be convoluted enough for the compiler not to recognize that this was
actually bzero() in disguise. Understood.

But then why there had been optimized assembler versions of OPENSSL_cleanse()
is beyond me. Did someone not trust the C obfuscation?

1 files changed, 0 insertions, 44 deletions

diff --git a/src/lib/libcrypto/pariscid.pl b/src/lib/libcrypto/pariscid.pl
index bfc56fdc7f..38985afbac 100644
--- a/src/lib/libcrypto/pariscid.pl
+++ b/src/lib/libcrypto/pariscid.pl
@@ -87,50 +87,6 @@ OPENSSL_wipe_cpu
         .PROCEND
 ___
 {
-my $inp="%r26";
-my $len="%r25";
-
-$code.=<<___;
-        .EXPORT OPENSSL_cleanse,ENTRY,ARGW0=GR,ARGW1=GR
-        .ALIGN  8
-OPENSSL_cleanse
-        .PROC
-        .CALLINFO       NO_CALLS
-        .ENTRY
-        cmpib,*=        0,$len,L\$done
-        nop
-        cmpib,*>>=      15,$len,L\$ittle
-        ldi             $SIZE_T-1,%r1
-
-L\$align
-        and,*<>         $inp,%r1,%r28
-        b,n             L\$aligned
-        stb             %r0,0($inp)
-        ldo             -1($len),$len
-        b               L\$align
-        ldo             1($inp),$inp
-
-L\$aligned
-        andcm           $len,%r1,%r28
-L\$ot
-        $ST             %r0,0($inp)
-        addib,*<>       -$SIZE_T,%r28,L\$ot
-        ldo             $SIZE_T($inp),$inp
-
-        and,*<>         $len,%r1,$len
-        b,n             L\$done
-L\$ittle
-        stb             %r0,0($inp)
-        addib,*<>       -1,$len,L\$ittle
-        ldo             1($inp),$inp
-L\$done
-        bv              ($rp)
-        .EXIT
-        nop
-        .PROCEND
-___
-}
-{
 my ($out,$cnt,$max)=("%r26","%r25","%r24");
 my ($tick,$lasttick)=("%r23","%r22");
 my ($diff,$lastdiff)=("%r21","%r20");