-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are vector data types supported? #1101
Comments
Hi @yblainm, thanks for your question and welcome to the ILGPU community. Unfortunately, these vector types are meant to be used inside GPU kernels for improved throughput in terms of compute and memory bandwidth. And yes, the main purpose of ILGPU is compiling kernels written in .Net into GPU code that can be run natively on most GPU devices. We are currently not supporting any of these high-level operations natively within ILGPU or ILGPU.Algorithms. However, @MPSQUARK is maintaining a high-level library around ILGPU being capable to turn vector and matrix operations into ILGPU-compatible kernels for acceleration. |
Thank you! This answers my question. It's good to know about the work on https://github.com/MPSQUARK/BAVCL which I'll be keeping an eye on. |
Hi @yblainm the BAVCL library is a project I am working on which aims to provide high level functionality and is based on ILGPU. What you describe, "similar to pythons numpy" but for C# using gpu acceleration, was the motivation behind it's development. |
Hi!
I see that there's been this branch merged #1023 which piqued my interest in this library, which as I understand it is primarily meant for JIT compiling kernels written in C# for various backends.
My question is: does ILGPU support vectorized operations and array math similar to Python's numpy, or NumSharp since the recent work on Vector types? I'm quite inexperience in writing kernels and am not very familiar with this codebase, plus I can't quite find documentation that explains it, though maybe I haven't searched well enough.
Thanks for your work and attention!
The text was updated successfully, but these errors were encountered: