invoke glVertex3f,-0.5,-0.5,0.0  ; GLfloat is single-precision
invoke glVertex3f,0.5,0.0,0.0
invoke glVertex3f,0.0,0.5,0.0
    

invoke glVertex2i,     0,0   ; GLint is 4-byte singed
invoke glVertex2i,    1,0
invoke glVertex2i,       1,1
    

macro invoke func,p1,p2,p3,p4,p5,p6
{
if ~ p1 eq
 mov rdi,p1
end if
if ~ p2 eq
  mov rsi,p2
end if
if ~ p3 eq
  mov rdx,p3
end if
if ~ p4 eq
  mov rcx,p4
end if
if ~ p5 eq
  mov r8,p5
end if
if ~ p6 eq
   mov r9,p6
end if
call [func]
}
    

Strange, someone responded but now their post isn't there anymore...

Anyways, using the vector forms of glVertex didn't get me anywhere. I either get nothing at all, or the verts are way off-screen.

I'm stumped.

Solved. I went through all of the glVertexXXX's until one worked.
Turns out that glVertex3fv works with floating point values defined as doubles in the data section.
Couldn't get any of the others to work.

bitshifter, this is 64-bit code and it is Linux forum so no stack nor stdcall (32-bit code typically use cdecl) is commonly used here.

bitshifter, this is 64-bit code and it is Linux forum so no stack nor stdcall (32-bit code typically use cdecl) is commonly used here.

eilenbeb, I think that float values are passed in xmm registers.

[edit]Yep, xmm registers. Take a look at this: http://board.flatassembler.net/topic.php?t=10553 . I have no reasons to suspect about the correctness of the macros, but since perhaps them were not extensively tested some things may be wrong so make sure to read the Linux ABI (some post there has a link). Also note that fasm now has extended support for ELF so you no longer need to create raw binaries as in those macros.[/edit]

[edit2]Well, the link is not there so here it is: http://www.x86-64.org/documentation/abi.pdf . In a quick look I think I saw that kohlrak's invoke uses all of the xmm registers to pass arguments but the specs uses from xmm0 to xmm7 only.[/edit]