#include <iostream>
#include <windows.h>

int main()
{
    std::cout << GetTickCount();
}    

format PE console
entry start

include 'win32a.inc'

section '.data' data readable writable

buf     rb      10
        db      0
fmt     db      '%d'
len     dd      ?
dummy   dd      ?

section '.code' code readable executable

start:
        call    [GetTickCount]
        push    eax
        push    fmt
        push    buf
        call    [wsprintf]
        mov     dword [len], eax
        push    -11
        call    [GetStdHandle]
        push    0
        push    dummy
        push    dword [len]
        push    buf
        push    eax
        call    [WriteConsole]
        push    0
        call    [ExitProcess]

section '.idata' import readable writable

 library kernel32, 'KERNEL32.DLL',\
         user32, 'USER32.DLL'

 import kernel32,\
        GetStdHandle, 'GetStdHandle', \
        WriteConsole, 'WriteConsoleA', \
        GetTickCount, 'GetTickCount', \
        ExitProcess,'ExitProcess'

 import user32,\
        wsprintf, 'wsprintfA'    

descriptive_name_for_value = -11
;...
push descriptive_name_for_value    

And now stuff this miracle in c++ into the disassembler and be disappointed in this short line.
Everything really will eventually come down to calling these WinAPI, but before that, c++ will do 100500 manipulations and checks with this data.

I think it would be clearer if the -11 magic value was made into a constant definition.

Code:

descriptive_name_for_value = -11
;...
push descriptive_name_for_value    

What does -11 represent?

add eax,ebx
rcr eax,1 ; (eax + ebx) / 2 without failure due to overflow    

mul edx ; use full result in edx:eax    

rep movsd    

        call    [GetTickCount]
        ;push    eax
        ;push    fmt
        ;push    buf
        cinvoke wsprintf,buf,fmt,eax
        mov     dword [len], eax     
    

A correction to the code at Post #1, should have used C calling convention for wsprintfA

Code:

        call    [GetTickCount]
        ;push    eax
        ;push    fmt
        ;push    buf
        cinvoke wsprintf,buf,fmt,eax
        mov     dword [len], eax     
    

Thanks @sinsi for your confirmation on the other thread.

call [wsprintf]
add esp, 0ch
    

After disassembly, cinvoke is actually

Code:

call [wsprintf]
add esp, 0ch
    

Why can't I use ccall?

 call wsprintf ; <- note there are no square brackets []    

FlierMate11 wrote:

After disassembly, cinvoke is actually

Code:

call [wsprintf]
add esp, 0ch
    

Kind of. The value 0ch is the three parameters pushed onto the stack beforehand. 3 * 4 = 12 bytes to add to esp.

FlierMate11 wrote:

Why can't I use ccall?

Because it encodes to this:

Code:

 call wsprintf ; <- note there are no square brackets []    

So you end up calling the data pointer, instead of the value stored in the data pointer.