On 14.07.2014 20:49, Andreas Kloeckner wrote:
elodw a...@pdauf.de writes:
Probably neither, since it's a two-index loop. I.e. you should probably
write that one from scratch to be able to map both i and j to CUDA axes.
Hope that helps,
Andreas
Thank You Andreas,
perhaps You know a Source in
Dear All,
Sorry to interrupt you by this way.
When I tried to test the sample code GlInterop.py, I met a problem as below:
---
File GlInterop.py, line 15, in module
LFC liufubu...@gmail.com writes:
Dear All,
Sorry to interrupt you by this way.
When I tried to test the sample code GlInterop.py, I met a problem as below:
---
Dear LFC,
LFC liufubu...@gmail.com writes:
I did the command rm -Rf build and setup.py build and setup.py
install.
But I sill have the same problem. I don't know why.
First, please make sure to keep the list cc'd, for archival. Next,
please post a complete build log to some pastebin and
Dear Andreas,
I switch on CUDA_ENABLE_GL in the line 47 in the ~/pycuda/pysetup.py
like this:
Switch(CUDA_ENABLE_GL, True, Enable CUDA GL interoperability),
And, I did rm -Rf build and setup.py build.
The complete build log is in the link: http://www.pastebin.ca/2821498
Thank you.
LFC
On