| What I wanted to point out is that if it means that you plan to submit more | AMD64 code to OpenSSL, then keep in mind that it's expected to be at the | very least position independent and preferably support both Win64 and | Linux ABIs and assemblers (see crypto/rc4/asm/rc4-amd64.pl for an | example).
Sure.
On one hand, I like the power of mixing perl & asm, but on the other hand mixing both languages leads to a really ugly syntax :)
Yes, it is, which why I wrote "preferably." Yet, whenever possible consider at least parameterizing the code, so that it can be easily adapted for that another ABI. E.g. instead of using real register names, use own symbolic names. Something similar to what you find in the very beginning of crypto/rc4/asm/rc4-amd64.pl: $inp, $out, $len, etc. Point is that it might worth throwing in a "general purpose" converter from GNU assembler and MASM syntax, in which case "parameterized" code for Linux would be sufficient. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
