> 2/ for MIPS, I just left the AES and BN : > > - AES currently supporting mips32 gcc only, since I cannot test it on > any other systems. > You could adapt it to your other mips machines, if you want to. > > - BN for mips32 since I find this framework much cleaner and more > readable than the generated mipspro code. > Anyway, both work.now
You can omit both AES and BN for MIPS. As for BN, there is no point in having two modules, when single module, bn/asm/mips.pl, works for complete range of platforms. As for AES, it's really easier for me to write new one from scratch, paying attention to multiple ABIs, endian neutrality, stack unwindability, code position independence, etc. etc. etc., than to fix yours. As I don't have access to little-endian MIPS, I'd like to reserve for option to ask you test it at some later point. A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
