Displaying 2 results from an estimated 2 matches for "vec3_cross".
2011 Aug 12
1
[LLVMdev] Using sret AND thiscall calling convention
...for win32 ABI, which says that the
first parameter should be a pointer to the return value:
%vec3 = type <{ float, float, float }>
define void @CPP_Return_Struct(%vec3* %v1, %vec3* %v2) inlinehint
alignstack(16) {
ENTRY:
%"@0" = alloca %vec3, align 4
call x86_thiscallcc void @vec3_Cross(%vec3* sret %"@0", %vec3* %v1, %vec3*
%v2)
ret void
}
declare x86_thiscallcc void @vec3_Cross(%vec3* sret, %vec3*, %vec3*) align 2
It seems that the code generated by the JIT takes the first parameter for
the this value because of the X86_thiscall calling convention. However, in
this...
2011 Aug 12
1
[LLVMdev] Using sret AND thiscall calling convention
...first parameter should be a pointer to the return value:
>
> %vec3 = type <{ float, float, float }>
>
> define void @CPP_Return_Struct(%vec3* %v1, %vec3* %v2) inlinehint
> alignstack(16) {
> ENTRY:
> %"@0" = alloca %vec3, align 4
> call x86_thiscallcc void @vec3_Cross(%vec3* sret %"@0", %vec3* %v1, %vec3*
> %v2)
> ret void
> }
>
> declare x86_thiscallcc void @vec3_Cross(%vec3* sret, %vec3*, %vec3*) align 2
>
> It seems that the code generated by the JIT takes the first parameter for
> the this value because of the X86_thiscall...