include 'somemacro.inc'

getsomethingdone    <--- from the past I have known this to use 3 Bytes pushed onto the stack.

pop ( a register )     < do I need to call pop 3 times to clear out the stack ?
pop ( a register )
pop ( a register )

hlt

--------------------------
( THIS IS THE MACRO INC FILE )

macro getsomethingdone
{
do something here
}
    

macro clear [reg]{
forward
  xor reg, reg
}

clear eax, ebx, ecx, edx, esi, edi ; This does not affect the stack in any way at all, no bytes are never reserved in stack and none is freed neither.    

There is something odd here, how do you manage to push 3 bytes onto stack when actually only word, dwords and qwords (64-bit mode only) is possible?

pop reg instruction will work with 16-, 32- and 64-bit registers so any combination will either leave some bytes not popped out or you'll pop out one or more bytes in excess.

PS: I did not understand much what has this to do with macros so I better clarify also this:

Code:

macro clear [reg]{
forward
  xor reg, reg
}

clear eax, ebx, ecx, edx, esi, edi ; This does not affect the stack in any way at all, no bytes are never reserved in stack and none is freed neither.    

xor eax, eax
xor ebx, ebx
xor ecx, ecx
xor edx, edx
xor esi, esi
xor edi, edi    

push [x]
push [y]
push [z]
;do something...
pop (e)ax
pop (e)ax
pop (e)ax
    

push [x]
push [y]
push [z]
;do something...
add (e)sp, (sizeof_machineword * 3)
    

Just to re-iterate:
Macros are not subroutines. They do not get CALL'd and RET'd from.
They are just replaced by in-line code during assembly.
So every instance of a macro just increases the size of the executable binary.