3 ms·
I'm probably missing something, but looking at: https://boringssl.googlesource.com/boringssl/+/master/crypto/aes/asm/ https://boringssl.googlesource.com/boring
by e12e 10y ago
I'm probably missing something, but looking at:
https://boringssl.googlesource.com/boringssl/+/master/crypto/aes/asm/ https://boringssl.googlesource.com/boringssl/+/master/crypto...
and in particular:
https://boringssl.googlesource.com/boringssl/+/master/crypto/aes/asm/vpaes-x86_64.pl https://boringssl.googlesource.com/boringssl/+/master/crypto... and https://boringssl.googlesource.com/boringssl/+/master/crypto/aes/asm/bsaes-x86_64.pl https://boringssl.googlesource.com/boringssl/+/master/crypto...
I don't see how this is any improvement on just writing plain assembler? Apart from the perl-style comments, is this any cleaner than say, some code compiled with yasm?
[ed: I guess what I'm missing is that there's probably more similarities between the x86 flavours and ARM flavours -- but I still think one would need to look at, and understand, the generated assembly for each platform in order to audit the code. So I still wonder a bit about what the gain is.]
- wolf550e 10y agoCan the Perl output in different syntaxes for different assemblers?