search for: spirkrnl

...the exception of structures, no lowering or expansion is allowed. Structures are passed as a pointer to struct with the byval attribute set. Functions marked with spirfunc calling convention can only be called by another function marked with either spirfunc or spirkrnl calling conventions. Functions marked with spirfunc calling convention can only call functions marked with spirfunc or spirkrnl calling conventions. Functions marked with spirfunc calling convention can only have zero or 1 return values. Func...

...are passed as is to the function with the exception of structures, no lowering or expansion is allowed. Structures are passed as a pointer to struct with the byval attribute set. Functions marked with spirfunc calling convention can only be called by another function marked with either spirfunc or spirkrnl calling conventions. Functions marked with spirfunc calling convention can only call functions marked with spirfunc or spirkrnl calling conventions. Functions marked with spirfunc calling convention can only have zero or 1 return values. Functions marked with spirfunc calling convention are only vi...

Hi Boaz, I have a couple of specific questions: (a) You mention special calling conventions and adding them to LLVM. What are their semantics? And what is their purpose? (b) Why disallow type conversion for vector types? (ss. 3.3) Cheers, James On Tue, 2012-09-11 at 12:56 +0100, Ouriel, Boaz wrote: > Hi All, > > In continuation of the previous SPIR introduction email here is a link

Hi All, In continuation of the previous SPIR introduction email here is a link to the specification: http://www.khronos.org/registry/cl/specs/spir_spec-1.0-provisional.pdf The first topic which we would like to discuss is "SPIR portability". I will send soon an additional mail which will help in leading the discussion on this topic. Thanks and happy reading, Boaz -----Original