![]() ![]() I have never heard the term "OpenCL C" before, but I admit I am not an expert on OpenCL. ![]() I had not heard of SPIR before - this appears to be some sort of intermediary between the programmer and OpenCL - I am somewhat baffled as to what problem it is trying to solve. It's quite possible that I'm missing the big picture here so please feel free to correct whatever I'm not catching. ![]() That sounds challenging but not totally infeasible knowing that OpenACC to SPIR is on its way. However, the language semantics must be mappable to SPIR and satisfy the constraints of OpenCL target systems.Īs I understand it that would require replacing, in the SPIR Reference Flow, the OpenCL C to SPIR IR generator by an OpenCL Fortran (?) to SPIR one. The alternative language could be many things, such as an established language (like FORTRAN), an exotic domain specific language, or a single source programming environment with automatic code partitioning. There is no need to generate OpenCL C as an intermediate. What set of problems is SPIR supposed to solve?Įnable third-party code generation targeting OpenCL platforms without going through OpenCL C:įor example, a compiler for an alternative device language (not OpenCL C) can generate SPIR and have it run on any OpenCL backend that supports the cl_khr_spir extension. I was actually thinking about kernels in Fortran, excerpt from the SPIR FAQ: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |