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

the future ? #4

Open
woncount opened this issue Jun 23, 2013 · 2 comments
Open

the future ? #4

woncount opened this issue Jun 23, 2013 · 2 comments

Comments

@woncount
Copy link

Quoting: "In an ideal world, the Clyther developers would move the core such that it was built on top of PyOpenCL, so we wouldn't have to choose, and to avoid duplication of labor. I doubt that will ever happen, though."
http://stackoverflow.com/a/4869923

Clyther looks like the most straightforward Python/OpenCL option, despite not being very complete, it is already very powerful and useful. However, it hasn't been updated in quite a while apparently. Given the ideas and features discussed on the website, I was wondering if it might be a feasible option to implement Clyther either on top of PyOpenCL or possibly llvm/llvmpy, llvm is already being used by AMD/NVIDIA to compile OpenCL and the tool chain is fully exposed, so that Python bytecode could be transparently processed and turned into corresponding CL kernels.

@srossross
Copy link
Owner

When I created CLyther, PyOpenCL was in it's infancy so I created my own OpenCL Python bindings https://github.com/srossross/oclpb which are separate from the CLyther Language translator. It should be feasible to remove the dependency on oclpb and replace it with PyOpenCL

@andreacortis
Copy link

Hello, what is the status of this project?

Andrea

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

No branches or pull requests

3 participants