> The fix for this in Android aosp's copy of openssl is file
> crypto/aes/asm/aes-mips.pl
> of change 40195,
> https://android-review.googlesource.com/#/c/40195/3/crypto/aes/asm/aes-mips.pl
Page in question contains a number of patches to .s files. They are not
necessary if you pass o32 to perl scripts, as you started doing. Well,
this is kind of stating obvious, but their presence is confusing.
Quoting the page:
"The upstream version of openssl builds for a "n32" Mips abi"
This is misleading statement. MIPS scripts support and can generate code
for *all* MIPS ABIs, not only n32. The target ABI should be passed as
additional argument. And after reviewing the code it appears that
statement has to be reinforced: "target ABI *must* be passed as
additional argument." Because for *some* modules failure to do so
results in code not compliant with any ABI. Indeed, we can see if
($flavour=~/64|n32/) {} else {}, then $flavour=~/nubi/? and finally if
($flavour=~/o32/). If $flavour is undefined, script generates 32-bit
code that adheres to o32 register layout, but not o32 prologue. This
inconsistency deserves a fix, i.e. assigning a default value to
$flavour. Provided if-logic o32 is most appropriate candidate...
Therefore http://cvs.openssl.org/chngview?cn=22765.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
