Displaying 2 results from an estimated 2 matches for "float44".
Did you mean:
float4
2011 Nov 02
0
[LLVMdev] About JIT by LLVM 2.9 or later
空明流转 <wuye9036 at gmail.com> writes:
> Could I wrap LLVM with mingw and expose some C api to called by MSVC?
>
> And in mingw, I will override the signature float4 foo( float44 ) to
> float4* foo( float4*, float44* ); ?
>
> Is that OK?
If you pass and return the structs through pointers, you don't need
MinGW in the middle, you can use MSVC directly. Please note that using
MinGW will not fix the LLVM sret problem.
2011 Nov 02
5
[LLVMdev] About JIT by LLVM 2.9 or later
Hello guys,
Thanks for your help when you are busing.
I am working on an open source project. It supports shader language
and I want JIT feature, so LLVM is used.
But now I find the ABI & Calling Convention did not co-work with MSVC.
For example, following code I have:
struct float4 { float x, y, z, w; };
struct float4x4 { float4 x, y, z, w; };
float4 fetch_vs( float4x4* mat