KhronosGroup / KhronosGroup/SPIRV-Cross

Request: extend SPIRV-Cross to accept OpenCL dialect of SPIR-V..

Open
#984 6 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
GLSL
Stars
2.5k
Forks
713
Avg merge
2d 18h
Merged PRs (30d)
16

Description

Hi,
just seeing IWOCL 2019 keynote presentation slides:(https://www.khronos.org/assets/uploads/developers/library/2019-iwocl/IWOCL%20Keynote%20May19.pdf)
https://www.khronos.org/developers/library/2019-iwocl
in page 31 we see talks about possible plans for "OpenCL portability initiative on Apple":
![image](https://user-images.githubusercontent.com/669305/57945680-c849e380-78da-11e9-9314-7fff711c8e06.png)
i.e. a OpenCL->Metal shim as Neil mentions that OpenCL maps to Metal better than to Vulkan (for CL->Vulkan we have clvk in progress) and with Apple deprecated OpenCL support maybe of interest..
for that, the slide mentions "SPIR-V Cross would need to be expanded to handle OpenCL dialect of SPIR-V) so just asking here..
I don't know why he doesn't mention using also clspv project which already maps OpenCL C source to SPIR-V Vulkan dialect..
Maybe because project is not mature enough or because maybe because is not enough as OpenCL 2.1 allows feeding directly SPIR-V OpenCL "binary" kernels for which clspv is of not use..
sorry, just random thoughts.. :-)

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or entry point is named. Start with the linked IWOCL 2019 keynote, especially page 31, then assess the scope of extending SPIRV-Cross for the OpenCL dialect of SPIR-V. Done would mean a defined implementation plan and demonstrated support for the requested dialect.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.