> Mario Brandt <...> writes:
>
>> For 64 bit there is no ASM source available.
Mario must be referring to 0.9.8.
> Really? But what about crypto/aes/asm/aes-x86_64.pl? That looks like
> it'll create ASM for WIN64, and appears to (in tmp32dll I have an
> aes-x86_64.asm).
1.0.0 has assembler support for VC-WIN64A.
> ... tmp32dll\x86_64cpuid.asm? In mine, line 144 (the one the
> assembler's complaining about) is like this (whitespace may vary because
> I'm typing this, reading from rdesktop):
>
> $L$ret:: DB 0F3h,0C3h ;repret
The line looks like one generated for ml64. Even though ml64 is not
unsupported, it's not periodically tested. Meaning that eventual
problems are fixed upon user feedback. Like this one. Thanks for report.
> The build succeeds if I install NASM, so it's no big deal, I guess.
Basically the word is "in case of doubt/trouble, use nasm."
> I
> suspect it's another minor bug in a perl script somewhere, though, which
> seems worth fixing.
Verify following:
--- crypto/x86_64cpuid.pl 24 Jan 2010 14:54:24 -0000 1.15
+++ crypto/x86_64cpuid.pl 13 Apr 2010 12:19:34 -0000
@@ -152,7 +152,8 @@
sub \$1,$arg2
lea 1($arg1),$arg1
jnz .Little
-.Lret: ret
+.Lret:
+ ret
.align 16
.Lot:
test \$7,$arg1
If you could verify the rest of build with ml64, it would be
appreciated. To switch back to ml64 make sure that nasm is *not* on your
%PATH% and re-run ms\do_win64a.bat. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
