Hello all, my question aims to those guys who had already tried to create DLL in new 64-bit format, and especially (if he will find time to answer) to mr. Privalov...
Problem is that if dll body contains macro 'proc', fasm 1.64 is not able to compile DLL, saying 'Illegal instruction' and pointing me to the first line with 'proc' macro. I am using 'format PE64 GUI DLL'.

As I understand this happens because in 'proc' macro still stands 'ebp' instead of 'rbp' and so on? Am I right? But correcting proc32.inc does not give anything
Thanks for attention

Sorry, forgot to mention: my systyem is
WIndows XP Prof x64 on AMD Athlon64 3000+ Venice

As the name says, proc32.inc is designed for 32 bit. The proc64.inc is not finished yet, and so I have not yet made it available to the public.

Thank you Tomasz, but how could I solve this problem? Only wait for new version? Sorry for time you spent on me

You can construct the procedure manually (also depending on the calling convention you want to use to call it), using the pure labels and standard instructions only.

If you want some example, please specify, how do you plan to call your procedures.

Yes I already used this way with pure labels, but i got error 'illegal instruction' at the line
'export 'testdll64.DLL',ForwardStepTruncated,'ForwardStepTruncated' '... So I cannot export my so-called 'procedure'! If you'll be so kind, here is my code example... I plan to call fast and optimized DLL procedure from a Visual Basic 6 program... [It has to do with signal propagation in a neural network... Written in assembler DLL function works with defined in VB program's memory array, and writes calculations in the another array. Pointers to this array (and some other params) are stored on the stack, and further passed to this procedure ] How can I get this code to compile?? Thanks in advance!



format PE64 GUI dll
entry DllEntryPoint

section '.code' code readable executable



DllEntryPoint: ; hinstDLL,fdwReason,lpvReserved
mov rax,0
ret

ForwardStepTruncated:
;!!! My procedure sarts here!
;here stack parameters
mNet equ rbp+16
dt_ptr equ rbp+24
V equ rbp+24
;........................
dt_sent equ r14
;prolog
push rbp
mov rbp,rsp
;end prolog
finit
fld1

mov rax,[dt_ptr]
mov i,0
mov dt_sent,rax
Next_i:
;.......
;.......
cmp rax,i
jne Next_i

mov rax,1
ret
;ForwardStepTruncated endp

section '.edata' export data readable

export 'testdll64.DLL',ForwardStepTruncated,'ForwardStepTruncated'

section '.reloc' fixups data discardable

You have to include export.inc to have the "export" macro. It is bitness neutral, so you can use it with 64-bit PEs aswell.

The macro packages that can be used with both PE and PE64 don't have the "32"/"64" at the end of names, like export.inc; the ones that can be used with Win32 PE files end with "32", like import32.inc and proc32.inc. I will add their equivalents for 64-bits in the future updates of the fasm for Windows package (the package may get updated with changed includes/examples even when the version of assembler stays the same).

Thank you very much,Tomasz! I was really stupid! Wish you good luck, keep it real

By the way: you have something else wrong surely. Here: What is that 'i' and shouldn't it be enclosed within aquare brackets '[]'?

2 Reverend:
Thanks, i published not all code i have written This junk was only for illustrating!
But u're right, i missed brackets with i

Hello Anatoly,

Did you manage to create a 64-bit DLL?

I have been trying with no success. Even I could compile and export funtions in my 64-bit DLL, Windows x64 says invalid windows image for my DLL.

If someone could copy-paste the code to create the most basic DLL for x64 I will be really happy

Thanks.