-
Notifications
You must be signed in to change notification settings - Fork 80
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
Tests fail for Raspberry Pi Zero #107
Comments
About the test passage, VC4CL is not complete, so while I agree having failing own tests may be confusing, other tests won't pass 100% too. E.g. currently it passes around 90+% of boost/compute tests, some only after fixing or modifying the tests to work on the platform and IIRC about 2/3 of OpenCL piglit tests. Similarly the OpenCL-CTS tests are largely passed, but with some major holes (e.g. anything non-trival math related). |
.1. No it does not, because there still is a line .4. Wouldn't it be better to create simple "2 + 2" example to verify if the library is working or not? Everyone says about boost tests and 90% of support. I don't know much about boost, I am interested if my program will work or not. I need to verify I have right compiler, right kernel, right firmware and right everything. And when I see "clCompileProgram failed" I get a feeling that something has gone terribly wrong and the whole thing doesn't work. .5. Well, I had the idea that maybe official programs will be executed without problems, so I played with programs from .6. Okay, I finally brought it to work, and I want to say that VC4CL is extremely unfriendly. All of this still applies to source from 2021/09/14. Should I build the latest? |
Oh right, missed that one. Does the header file
Not sure if I understand you correctly, but if you want to run own code then I cannot guarantee that it works, since that depends on so many things. You will have to try it out and if the compilation fails then it could very well be a bug/missing feature in VC4C. The issue with the prefixes is that there are basically 2 ways of using any OpenCL implementation: directly or via an ICD loader. If you want to use it directly, configure CMake with As for the source code version, I would always recommend to use latest master. |
I reinstalled my system, I have Buster now. there is no
Well, it would be nice if you could provide some simple program and say "This one is one true way. If it is compiled and works, other programs written in similar way may probably also work. If it is not compiled or doesn't work, it's your problem". Instead you provide no examples and don't guarantee that user's code works. Totally fair from your side, but it doesn't help anybody in using the library. Thanks for |
About which software should work: Any OpenCL client application which works on other OpenCL implementations and does not use some implementation specific features or unsupported extensions shoudl work. If it does not, it is likely a bug in VC4CL. I just tested on a fresh installation of Bullseye and besides one fix with the header paths (which I will probably commit today or so) it compiles fine. But Buster is definitively tested more extensively. |
Okay, I tried this example, started it with |
Hello. I'm trying to run OpenCL on Raspberry Pi Zero with Raspbian (Debian Buster). I know that the library was not designed for Zero, but since this guy claimed it worked for him, I decided to give it a try. So here is what I discovered:
VC4CL
cannot be built on latest Raspbian, because it doesn't have/opt/vc/
. Not sure if it is supposed to be there or they moved it to other place.VC4C
throwsunexpected reloc type 0x03
error. Could be fixed with '-DCMAKE_CXX_FLAGS=-fPIC'.VC4CL
commit with "stable" tag cannot be compiled:Program.cpp
needsOptional.h
but can't find it. Can be fixed easily.TestVC4CL
from 2021/09/14 passes only 36.6% of tests./opt/vc/bin/container_test
I discovered that nowTestVC4CL
passes 54% of tests.Could you please comment this situation?
Even if it doesn't work for me, you do a great job. Thank you.
The text was updated successfully, but these errors were encountered: