ocl VS GLSL

Please note that OpenCL consists of two parts: host API and a separate language which is used to write kernels (code which is going to be offloaded to devices). OpenCL specification describes host APIs as C-style APIs and that is what implementors has to provide. However, there are number of various libraries which provides bindings for other languages: - C++ - Python - Go - Rust

ocl

I don't know a lot about Rust, but this looks like a valid set of OpenCL bindings for Rust: https://github.com/cogciprocate/ocl

If you prefer an open alternative to CUDA, there are complete, easy to use und well documented bindings for opencl: https://github.com/cogciprocate/ocl/

- https://github.com/cogciprocate/ocl/issues/202

I use Rust with OpenCL (ocl). And I am still in college studying CS. It takes a while to setup OpenCL depending on what you want to do with it. But performance benefits are well worth it. On average I can backtest 4 years of data with 1 minute candles in about 8.745 ms for typical RSI indicator. This is done on i5-3320m CPU (not iGPU). Took me a year to build it. Was also learning rust with it. My project has many features so you probably can do it in half amount of time or even less. Currently the project has 21k in Rust and 2k lines in OpenCL.

You're looking for this repo

You have access to physical (u64) global memory pointers through buffer_reference in GLSL, note you should be using buffer_reference2

On April 27, 2023 the Vulkan® Ray Tracing TSG released the VK_KHR_ray_tracing_position_fetch extension, which exposes the ability to fetch vertex positions from an acceleration structure hit when tracing rays. The SPIR-V SPV_KHR_ray_tracing_position_fetch and GLSL GL_EXT_ray_tracing_position_fetch extensions have also been released to provide SPIR-V and GLSL support for this functionality.

You can also have general extensions that are only supported on some hardware, for instance NVIDIA supports all of these extensions on OpenGL that add support for Vulkan's thread subgroup operations while AMD only supports these extensions and a few others that add support for similar features to the extension that NVIDIA supports, but with way more restrictions.

GL_NV_ray_tracing is a vendor extension, but it does exist.

According to this document, one should be able to extract those values through

The reports of my death are greatly exaggerated

https://github.com/KhronosGroup/GLSL/blob/master/extensions/...

I don't think there's away. For Vulkan, there's GL_EXT_nonuniform_qualifier which allows you to index with gl_InstanceIndex but AFAIK it's not available for OpenGL.

AMD hardware works a little differently, and for that you have to write a waterfall loop with subgroup instructions to get the correct behavior (since GL_EXT_nonuniform_qualifier doesn't exist in OpenGL GLSL). The loop might look like this (you would use it the same way as NonUniformEXT in Vulkan GLSL).