Mystery with duplicated INCLUDE winsgui.htm explained: The library belongs to PROGRAM realm , which means that it contains only constant symbols and structures definitions (not macros). The second INCLUDE is encapsulated in PROGRAM..ENDPROGRAM block, and when assembly of PROGRAM starts, it begins wi...

The list of macro arguments is available in %MACRO..%ENDMACRO body as automatic variable %* . You cannot use automatic variable outside the macro but its contents (the whole list) may be copied to standard user-defined %variable and then used anywhere below the macro. fake %MACRO arg1,arg2,arg3 %fak...

Yes, callee is the owner of shadow space (ShSp), from the moment when it's been called . The red quotation says that I (in the role of WinABI caller), having just allocated ShSp, cannot save anything to it, then call the function and expect that the saved information survived intact in ShSp across t...

Thank you. Already done. Now onto the next problem: ;===================================================================================== HEADER EUROASM CPU=X64, AMD=ON Test PROGRAM Format=PE, Subsystem=GUI, WIDTH=64, Entry=START INCLUDE winabi.htm, wins.htm, winsgui.htm, fastcall.htm, cpuext.htm,...

ar18 wrote: ↑03 Sep 2018 13:12 Thank you. Already done. Now onto the next problem:

I moved the question to a new topic Test PROGRAM Format=PE reports E6101.

I worked with the author of GoASM regarding this and his approach was to prefix those particular parameters with a Q or a D to indicate if it was a float or double, e.g. -- invoke fnTest,Q [dblVar], D [fltVar],,,and so on . If you'll satisfy with something like invoke fnTest, Q:dblVar, D:fltVar,,,a...

Actually, those data types are with us all the time. I'm not seeing it. A QWORD is not the same thing as a REAL8 or double-precision float. They are the same size in bytes, but they are not interpreted in the same way or in the way that a Win64 compliant needs it to be interpreted. Most of the func...

That is incorrect code. The registers are never put on the shadow space stack by the caller, but always by the callee. Seems I remember someone telling me to RTFM, in this case it should be the Win64 ABI manual :) . This is one of the problems with the WinAPI macro in 64-bit mode. It is the functio...

Release date: 2018 Sep 1 TimeStamp: 1535760000 File size: 3838803 File hash MD5: E56A63A7060DAAD39603558FF960E058 What's new: New attribute REGTYPE# introduced. Macro WinAPI in macrolibrary winabi.htm was enhanced with passing values in XMM. Alphabetic Index was completed with automatic %variables a...

I would like to suggest that for Win64 support in €ASM, could you provide a fastcall, cdecl, stdcall, and vector directive/macro for the calling convention, or at least make it possible so that a macro could be written by users to do this? I think any convention is already possible at macro level. ...