In message <98f571de-f47e-6259-f1ac-792ebed3e...@wisemo.com> on Thu, 27 Dec
2018 10:12:34 +0100, Jakob Bohm said:
> On 24/12/2018 19:08, Richard Levitte wrote:
> > In message <3fc4d543-d71a-8c22-566a-d902c4f7d...@gmail.com> on Mon, 24
> > Dec 2018 13:17:51 +0100, Gisle Vanem said:
> >
> >>
On 24/12/2018 19:08, Richard Levitte wrote:
In message <3fc4d543-d71a-8c22-566a-d902c4f7d...@gmail.com> on Mon, 24 Dec 2018
13:17:51 +0100, Gisle Vanem said:
Richard Levitte wrote:
I experimented some more. I figured the "auto" does not work.
But this works:
perl
In message <3fc4d543-d71a-8c22-566a-d902c4f7d...@gmail.com> on Mon, 24 Dec 2018
13:17:51 +0100, Gisle Vanem said:
> Richard Levitte wrote:
>
> >> I experimented some more. I figured the "auto" does not work.
> >> But this works:
> >>perl crypto\aes\asm\aesni-x86_64.pl nasm > tmp-file.s
>
Richard Levitte wrote:
I experimented some more. I figured the "auto" does not work.
But this works:
perl crypto\aes\asm\aesni-x86_64.pl nasm > tmp-file.s
diff tmp-file.s crypto\aes\aesni-x86_64.asm
No diffs.
Why does the the generation of .asm-files be so damn hard to
figure out? Some
In message on Fri, 21 Dec 2018
15:45:23 +0100, Gisle Vanem said:
> I'm trying to understand how the generation of ASM-files
> are done on x64. (I have no problems on x86).
>
> With the generated Nmake makefile from a
> perl Configure VC-WIN64A-ONECORE
>
> when doing a:
> nmake
I'm trying to understand how the generation of ASM-files
are done on x64. (I have no problems on x86).
With the generated Nmake makefile from a
perl Configure VC-WIN64A-ONECORE
when doing a:
nmake crypto\aes\libcrypto-lib-aesni-x86_64.obj
seems to do this:
set ASM=nasm
