[LLVMdev] SPIR Portability Discussion
nrotem at apple.com
Thu Sep 13 00:33:22 PDT 2012
So, linked-lists (Maybe an OpenCL 2.0 feature?) which are compiled with SPIR will take twice as much memory space. Right ?
I don't understand why you decided to focus on size_t, which can be optimized away in so many cases. I think that solving the pointer size problem is much more important.
>> Also, future OpenCL versions may introduce C++ features to the
>> language. You need to be prepared to supports these features in SPIR.
>> For example, c++ references may require SPIR to handle GEPs to structs
>> that contain size_t members.
> [Villmow, Micah] SPIR 1.0 targets OpenCL 1.2, so features outside of OpenCL 1.2 are also outside of the scope of SPIR 1.0.
I think that you need to present a general direction of how to solve this. It is also okay to say that placing size_t inside a struct forces it to be 64bits.
More information about the llvm-dev