Make bn/asm/x86_64-gcc.c gcc4 savvy. +r is likely to be initially
authorAndy Polyakov <appro@openssl.org>
Sun, 3 Apr 2005 18:53:29 +0000 (18:53 +0000)
committerAndy Polyakov <appro@openssl.org>
Sun, 3 Apr 2005 18:53:29 +0000 (18:53 +0000)
commit60fd574cdfa5e4984f1ec193775b869fe99f544c
tree69ff506c25dbf348cf5bddaebae34c2a278446d1
parent73705abc3411ac09aaea674a8fad35a019bc90f3
Make bn/asm/x86_64-gcc.c gcc4 savvy. +r is likely to be initially
introduced for a reason [like bug in initial gcc port], but proposed
=&r is treated correctly by senior 3.2, so we can assume it's safe now.
PR: 1031
crypto/bn/asm/x86_64-gcc.c