Skip to content
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

•_CUDAFor development plan #9

Open
ashermancinelli opened this issue Nov 30, 2021 · 2 comments
Open

•_CUDAFor development plan #9

ashermancinelli opened this issue Nov 30, 2021 · 2 comments
Assignees

Comments

@ashermancinelli
Copy link
Owner

The following system modifier is now available with limited support:

$ ./BQN -e '•Show (↕10) + •_CUDAFor ↕10'
⟨ 0 2 4 6 8 10 12 14 16 18 ⟩

What should the development plan be for CUDA/GPU support after the runtime is implemented on the device?

@ashermancinelli
Copy link
Owner Author

From Marshall on matrix:

You could handle blocks even, by replacing primitives that are loaded as constants. Well, you have to assume that it doesn't pull in primitives from outside variables. Probably best to scan the variable uses and reject anything that refers to outside variables anyway though.

@ashermancinelli
Copy link
Owner Author

This and all other accelerator options should be brought under the namespace •cxbqn. Perhaps:

   cu←•cxbqn.accelerate.cuda
   (↕10) + cu._for ↕10
⟨ 0 2 4 6 8 10 12 14 16 18 ⟩

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant