skyglow
Posts: 1
Joined: Mon Jan 15, 2018 2:01 pm

Re: OpenCL on the VideoCore IV!

Mon Jan 15, 2018 2:13 pm

Great work doe!

My comment may sound stupid but this could help solving some compilation issues of the test suites.
Building LLVM/Clang in Relese mode is preferred since it consumes a lot less memory. Otherwise, the building process will very likely fail due to insufficient memory. It’s also a lot quicker to only build the relevant back-ends (ARM and AArch64), since it’s very unlikely that you’ll use an ARM board to cross-compile to other arches. If you’re running Compiler-RT tests, also include the x86 back-end, or some tests will fail.

Code: Select all

cmake $LLVM_SRC_DIR -DCMAKE_BUILD_TYPE=Release \
                    -DLLVM_TARGETS_TO_BUILD="ARM;X86;AArch64"
from http://releases.llvm.org/5.0.1/docs/How ... OnARM.html

I'm trying to use your sources on openSuse 64bit. I'll post later on about success/failure.

paulreimer
Posts: 3
Joined: Mon Jan 15, 2018 1:47 am

Re: OpenCL on the VideoCore IV!

Mon Jan 15, 2018 5:01 pm

While I'm not familiar with GPGPU on the Pi (i.e. using OpenGL, not OpenCL), my experience on x86's has been that GPGPU/OpenGL performance can be quite a bit better than OpenCL (for certain problems), which is perhaps because the OpenGL drivers are more optimized for problems which are easily modelled to OpenGL primitives.

What are your thoughts on this regarding the RPi? Is that something that could also be benchmarked?

paulreimer
Posts: 3
Joined: Mon Jan 15, 2018 1:47 am

Re: OpenCL on the VideoCore IV!

Mon Jan 15, 2018 5:12 pm

Also, would this work on the RPi Zero family? pocl vs OpenCL benchmarks would be quite different there, yes? (e.g. OpenCL should stay the same, while pocl would have fewer cores to work with)

mic_s
Posts: 75
Joined: Sun Oct 26, 2014 4:15 pm

Re: OpenCL on the VideoCore IV!

Mon Jan 15, 2018 10:42 pm

would this work on the RPi Zero family?
Pi0, Pi2, Pi3 all the same VideoCore IV., so any benchmark (if based on the very VideoCore IV) will give the same result.
( That said, there is a very, very small difference between the GPU in Pi0 and the GPU in Pi3 :
Pi0 : The GPU is the „owner“ of the L2 Cache. Pi3 : Arm is the „owner“ of the L2 Cache. )
.

doe300
Posts: 42
Joined: Thu Dec 29, 2016 1:41 pm

Re: OpenCL on the VideoCore IV!

Tue Jan 16, 2018 9:42 am

paulreimer wrote:
Mon Jan 15, 2018 5:01 pm
What are your thoughts on this regarding the RPi? Is that something that could also be benchmarked?
Since there exists an OpenGL implementation for the RPi running on the VC4 as well as the VC4CL implementation, their relative performance could be tested with a benchmark yielding comparable results.
paulreimer wrote:
Mon Jan 15, 2018 5:01 pm
[...] my experience on x86's has been that GPGPU/OpenGL performance can be quite a bit better than OpenCL (for certain problems), which is perhaps because the OpenGL drivers are more optimized for problems which are easily modelled to OpenGL primitives.
I think this is to be expected out of various reasons:
  1. The code is run on graphic processors, for which OpenGL is explicitly written, OpenCL is also intended to run on FPGAs and CPUs. So OpenGL is fitted more precisely to the hardware-features and -limitations of GPUs
  2. OpenCL is expected to handle a lot more use-cases than OpenGL, so OpenGL can be better optimized for its more limited uses
  3. In OpenGL, time is of the essence (you want to guarantee a certain FPS), so optimizing it for performance is critical
  4. Lastly, AFAIK OpenGL is far more used than OpenCL, so focusing on optimizing OpenGL the smart choice from the vendors point of view

merlz42
Posts: 25
Joined: Sun May 13, 2012 1:19 pm

Re: OpenCL on the VideoCore IV!

Fri Jan 26, 2018 9:48 am

I'm having trouble getting this detected. Here's my whole build process:

Code: Select all

cd /opt && rm -rf * && git clone https://github.com/KhronosGroup/SPIRV-LLVM.git && cd SPIRV-LLVM && git checkout khronos/spirv-3.6.1 && mkdir build && cd build && cmake ../ -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_RUNTIME=Off -DLLVM_INCLUDE_TESTS=Off -DLLVM_INCLUDE_EXAMPLES=Off -DLLVM_ENABLE_BACKTRACES=Off -DLLVM_TARGETS_TO_BUILD=ARM && make -j2
cd ~/tmp && rm -rf * && git clone https://github.com/doe300/VC4CLStdLib.git && git clone https://github.com/doe300/VC4C.git && git clone https://github.com/doe300/VC4CL.git
cd VC4CLStdLib && cmake . && make -j2 && make install && cd ..
cd VC4C && cmake . && make -j2 && make install && cd ..
cd VC4CL && cmake . && make -j2 && make install && cd ..
This all executes correctly and I've got all the supporting packages installed. I installed the newer clinfo from source. Running sudo clinfo returns 0 platforms :-(

doe300
Posts: 42
Joined: Thu Dec 29, 2016 1:41 pm

Re: OpenCL on the VideoCore IV!

Fri Jan 26, 2018 10:39 am

merlz42 wrote:
Fri Jan 26, 2018 9:48 am
This all executes correctly and I've got all the supporting packages installed. I installed the newer clinfo from source. Running sudo clinfo returns 0 platforms :-(
See here, for the ICD loader to detect the implementation, there needs to exist a file in /etc/OpenCL/vendors/ with a single line containing the absolute path to the library (in this case libVC4CL.so) to load. This file should have been generated in your build-directory with the name VC4CL.icd and should have also been copied to the correct path with the make install command.

Can you check if /etc/OpenCL/vendors/VC4CL.icd exists and whether the library-path contained points to the correct library-file?

merlz42
Posts: 25
Joined: Sun May 13, 2012 1:19 pm

Re: OpenCL on the VideoCore IV!

Fri Jan 26, 2018 10:46 am

Code: Select all

$ cat /etc/OpenCL/vendors/VC4CL.icd 
/usr/local/lib/libVC4CL.so
$ ls /usr/local/lib/libVC4CL.so
/usr/local/lib/libVC4CL.so
$ ls -lah /usr/local/lib/libVC4CL.so
lrwxrwxrwx 1 pi staff 15 Jan 23 08:35 /usr/local/lib/libVC4CL.so -> libVC4CL.so.1.2
$ ls -lah /usr/local/lib/libVC4CL.so.1.2 
lrwxrwxrwx 1 pi staff 15 Jan 23 08:35 /usr/local/lib/libVC4CL.so.1.2 -> libVC4CL.so.0.4
$ ls -lah /usr/local/lib/libVC4CL.so.0.4 
-rw-r--r-- 1 pi staff 6.0M Jan 26 09:38 /usr/local/lib/libVC4CL.so.0.4

doe300
Posts: 42
Joined: Thu Dec 29, 2016 1:41 pm

Re: OpenCL on the VideoCore IV!

Fri Jan 26, 2018 11:59 am

The ICD-loader should find the libVC4CL.so, maybe it cannot load it.
Can you print the results of ldd /usr/local/lib/libVC4CL.so and see if all required libraries are found?

Can you also check if the programs v3d_info, v3d_dump_analyzer or VC4C work?

merlz42
Posts: 25
Joined: Sun May 13, 2012 1:19 pm

Re: OpenCL on the VideoCore IV!

Fri Jan 26, 2018 9:07 pm

This looks like it works. To detect libVC4CC, I needed:

Code: Select all

export LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib
This is weird since /usr/local/lib is set in ld.so.conf.

Similarly, I can run clinfo successfully now with:

Code: Select all

sudo LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib clinfo
This is with a default raspbian distro on raspberry pi 3.

naibaf7
Posts: 1
Joined: Thu Feb 01, 2018 1:23 am

Re: OpenCL on the VideoCore IV!

Thu Feb 01, 2018 1:24 am

I'm trying to add quirks/workarounds to OpenCL Caffe in order to get some networks working on RaspberryPI OpenCL:
https://github.com/naibaf7/caffe

mogu
Posts: 2
Joined: Fri Feb 16, 2018 9:09 pm

Re: OpenCL on the VideoCore IV!

Fri Feb 16, 2018 11:24 pm

Hello,

pocl developer here.. just stumbled upon this thread while randomly browsing the net :)
just a few observations...
  • @doe300 very impressive work! though i suspect you have a lot more to do if you actually plan on finishing it..
  • pocl supports other than CPU devices - in fact it supports three (NVidia cards via our CUDA backend, certain AMD hardware via HSA runtime, and a virtual device that's used to simulate hardware) so adding another shouldn't be a big issue, if anyone decides to do so..
  • I'd advise you to stay away from clPeak as a benchmark (and ignore all past results), at least until it's fixed. If you look at its OpenCL kernels here: https://github.com/krrishnarraj/clpeak/ ... rc/kernels you'll notice the author uses recursive macros to implement them, resulting in giant kernels with several thousand identical instructions. This causes several issues: 1) it's not even close to realistic benchmark, 2) certain LLVM optimization passes completely explode on this code (taking forever to compile), 3) it very easily overflows the L1 icache of the CPU/GPU, meaning you'll not be measuring FLOPS but rather how fast your CPU can execute from L2 while L1 is being trashed. If you look at the uploaded result files, you'll notice the results are all over the place and make no sense - that is a direct consequence.
Author claims he does it to fool the autovectorizer, but i found that isn't a problem, at least with LLVM+pocl. Replacing the recursive macros in clPeak with for loops (keeping the FLOPS per kernel identical), on Arch Linux + llvm 5 + pocl git master on RPi2 i got these results:

Code: Select all

[[email protected] b]$ /home/alarm/clpeak/b/clpeak --compute-sp

Platform: Portable Computing Language
  Device: pthread-cortex-a7
    Driver version  : 1.1-pre (Linux ARM)
    Compute units   : 4
    Clock frequency : 900 MHz

    Single-precision compute (GFLOPS)
      float   : 0.89
      float2  : 1.78
      float4  : 3.34
      float8  : 3.42
      float16 : 3.47
looks much more realistic than those old pocl results with 0.03 GFlops for all vector sizes, doesn't it ? ;) I haven't yet installed VC4CL, but in case anyone wants to try it, here's the clPeak patch i used (for SP benchmark only): https://pastebin.com/aHYrFage - i suspect VC4CL will also turn out to be much faster.

doe300
Posts: 42
Joined: Thu Dec 29, 2016 1:41 pm

Re: OpenCL on the VideoCore IV!

Sat Feb 17, 2018 10:20 am

mogu wrote:
Fri Feb 16, 2018 11:24 pm
@doe300 very impressive work! though i suspect you have a lot more to do if you actually plan on finishing it..
Thanks. Definitively, especially in the compiler and standard-library.
mogu wrote:
Fri Feb 16, 2018 11:24 pm
pocl supports other than CPU devices - in fact it supports three (NVidia cards via our CUDA backend, certain AMD hardware via HSA runtime, and a virtual device that's used to simulate hardware) so adding another shouldn't be a big issue, if anyone decides to do so..
I didn't know that. I suspect to port pocl to VC4, we would need to write a LLVM back-end for the VideoCore IV architecture, which I tried at first, but didn't get anywhere.
mogu wrote:
Fri Feb 16, 2018 11:24 pm
I'd advise you to stay away from clPeak as a benchmark (and ignore all past results), at least until it's fixed. If you look at its OpenCL kernels here: https://github.com/krrishnarraj/clpeak/ ... rc/kernels you'll notice the author uses recursive macros to implement them, resulting in giant kernels with several thousand identical instructions. This causes several issues: 1) it's not even close to realistic benchmark, 2) certain LLVM optimization passes completely explode on this code (taking forever to compile), 3) it very easily overflows the L1 icache of the CPU/GPU, meaning you'll not be measuring FLOPS but rather how fast your CPU can execute from L2 while L1 is being trashed. If you look at the uploaded result files, you'll notice the results are all over the place and make no sense - that is a direct consequence.
Thanks for the insight. Another thing I noticed is, that the generated code almost never executes both asymmetric ALUs in a single instruction, since every instruction depends on the previous one (e.g. for floating-point benchmark). But I don't know that much about benchmarks and - in contrast to some other benchmarking programs I've tested - the output of clpeak is actual useful.
mogu wrote:
Fri Feb 16, 2018 11:24 pm
Author claims he does it to fool the autovectorizer, but i found that isn't a problem, at least with LLVM+pocl.
Can't say much about that, since LLVM does not auto-vectorize the code for VC4CL. Which is either because I compile to LLVM IR and thus LLVM doesn't know the vectorization preferences of the destination architecture, or because the vectorization is done in the back-ends, which are not executed.
mogu wrote:
Fri Feb 16, 2018 11:24 pm
[...] but in case anyone wants to try it, here's the clPeak patch i used (for SP benchmark only): https://pastebin.com/aHYrFage - i suspect VC4CL will also turn out to be much faster.
Thanks, I will have to test that sometime.

mogu
Posts: 2
Joined: Fri Feb 16, 2018 9:09 pm

Re: OpenCL on the VideoCore IV!

Sat Feb 17, 2018 5:33 pm

doe300 wrote:
Sat Feb 17, 2018 10:20 am
I didn't know that. I suspect to port pocl to VC4, we would need to write a LLVM back-end for the VideoCore IV architecture, which I tried at first, but didn't get anywhere.
A LLVM backend would make things easier, but i think is not actually required. What pocl does is roughly 1) compiles OpenCL C to IR, 2) links the kernel library to it, 3) runs a bunch of optimizations on the IR, 4) hands over the resulting LLVM IR to the device driver. What the driver does with it is entirely up to the driver. The CPU driver compiles it to native code, the CUDA driver converts it to PTX, etc. So as long as the driver can take plain LLVM IR as input, it can be done. What is actually needed though, is a LLVM triple - i'm guessing the only usable for VC4 would be SPIR ?
or because the vectorization is done in the back-ends, which are not executed.
Well, the loop-vectorizer is an optimization pass, and so is the SLP vectorizer. Both are IR -> IR transforms, they are run before the backends are invoked.

spinoza1791
Posts: 2
Joined: Wed Feb 28, 2018 4:04 am

Re: OpenCL on the VideoCore IV!

Wed Feb 28, 2018 4:07 am

Great work! I see this released here: https://github.com/doe300/VC4CL

Have you found an implementation yet with YOLO or MobileNetSSD on the Pi? How can we take advantage of your OpenCL to run neural nets like these?

rpalandri
Posts: 1
Joined: Tue Mar 06, 2018 3:22 pm
Location: Nurnberg, Germany
Contact: Website Facebook Twitter

Re: OpenCL on the VideoCore IV!

Tue Mar 06, 2018 3:32 pm

Cool !

Have you seen the PONF Multiback Open Camera Project (www.ponfcamera.com) ?

We are developing a camera that shoots digital and film, and we are using a RaspberriPI Compute Module 3 to control Sony APS-C and Full-frame sensors.

Could we have a chat ?

madtom1999
Posts: 51
Joined: Mon Jul 29, 2013 4:37 pm

Re: OpenCL on the VideoCore IV!

Sat Mar 10, 2018 3:31 pm

spinoza1791 Caffe has an openCL port https://github.com/BVLC/caffe/tree/opencl so this may work with that.
I'm busy with other stuff but will try this asap. I'd be interested to see if there are any thermal issues with this.

Zenitur
Posts: 3
Joined: Fri Mar 16, 2018 7:27 pm

Re: OpenCL on the VideoCore IV!

Fri Mar 16, 2018 7:35 pm

Hello. This is compiled GCC 6 binary for Raspbian 8: https://yadi.sk/d/QUjNLTCx3Koo7o Just extract it into /opt, then run:

Code: Select all

export LD_LIBRARY_PATH=/opt/gcc-6.3.1/lib
Now libVC4CL.so.0.4 library installed from DEB package did't say that system's libstdc++.so.6 is too old! Also, nighly build are empty now, so there are download links:

Code: Select all

curl -OL https://47-106166771-gh.circle-artifacts.com/0/root/project/vc4c-0.4-Linux.deb
curl -OL https://47-106166771-gh.circle-artifacts.com/0/root/project/vc4cl-stdlib-0.4-Linux.deb
curl -OL https://47-106166771-gh.circle-artifacts.com/0/root/project/build/VC4C
curl -OL https://47-106166771-gh.circle-artifacts.com/0/root/project/build/libVC4CC.so.0.4
curl -OL https://47-106166771-gh.circle-artifacts.com/0/root/project/build/test/TestVC4C
curl -OL https://47-106166771-gh.circle-artifacts.com/0/root/project/vc4cl-0.4-Linux.deb
curl -OL https://27-106172036-gh.circle-artifacts.com/0/root/project/vc4cl-0.4-Linux.deb
curl -OL https://27-106172036-gh.circle-artifacts.com/0/root/project/build/libVC4CL.so.0.4
curl -OL https://27-106172036-gh.circle-artifacts.com/0/root/project/build/test/TestVC4CL
Please send me precompiled SPIRV-LLVM binaries. I'd spend much of my time for compiling of GCC 6 using this manual. I'm tired. Please, I'd prepared GCC for you, you will compile SPIRV-LLVM for me.

doe300
Posts: 42
Joined: Thu Dec 29, 2016 1:41 pm

Re: OpenCL on the VideoCore IV!

Sat Mar 17, 2018 7:01 am

I updated the instructions here to download the nightly builds.

Why did you compile GCC 6 from source? The latest Raspbian OS already includes GCC 6.3 by default.

spinoza1791
Posts: 2
Joined: Wed Feb 28, 2018 4:04 am

Re: OpenCL on the VideoCore IV!

Tue Apr 10, 2018 1:41 am

Any luck getting OpenCL to work with OpenCV for Pi? It would be amazing to offload OpenCV to GPU to allow the CPU to focus on the neural net calcs.

Micha1982
Posts: 261
Joined: Wed Oct 03, 2012 11:18 am

Re: OpenCL on the VideoCore IV!

Wed Apr 11, 2018 5:38 am

Hello,
this is interesting, so I gave this a try and followed the nightly-install-instructions, everything seems fine so far - the program I want to use it for (Mandelbulber2) recognizes the driver and VideocoreIV in its Options.

But it does not work. When I start to render something it crashes immediately and telling "bus access error"...but I do not know if that is driver-related or caused by Mandelbulber anyhow.

Whats more important to me at the moment is the following, if I start any program after I installed your OpenCL driver I now get a

Code: Select all

MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
in the terminal...but why and how to solve this? I do not know if its harmful, installed programs seems fine so far - but minutes ago I downloaded the latest ScummVm-2.0-package for the Pi for example, and if I try to start the file inside it tells me

Code: Select all

MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
Could not find ScummVM window for retrieving default display mode!
and does not start. I do not know if there is any context between this 3 mesa-messages and the not starting game (the older 1.9 from repository gives me the same 3 errors atm but is still starting fine) or the bus-access-error in Mandelbulbers OpenCL-renderer...maybe you have an idea.

I do further tests know with an older backup to be sure the message was not there, but I could not remember that I've read these 3 mesa-messages before installing the OpenCL-driver and as said being interested in finding out if there is a context between it and the problems or how to solve them.
Alles, was schiefgehen kann, wird auch schiefgehen.

doe300
Posts: 42
Joined: Thu Dec 29, 2016 1:41 pm

Re: OpenCL on the VideoCore IV!

Wed Apr 11, 2018 3:57 pm

Micha1982 wrote:
Wed Apr 11, 2018 5:38 am
But it does not work. When I start to render something it crashes immediately and telling "bus access error"...but I do not know if that is driver-related or caused by Mandelbulber anyhow.
I don't know where the error comes from. It sounds like a component close to the hardware (maybe Mailbox interface, etc.), but it is no error message generated from within VC4CL.
Micha1982 wrote:
Wed Apr 11, 2018 5:38 am
Whats more important to me at the moment is the following, if I start any program after I installed your OpenCL driver I now get a

Code: Select all

MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
in the terminal...but why and how to solve this? I do not know if its harmful, installed programs seems fine so far - but minutes ago I downloaded the latest ScummVm-2.0-package for the Pi for example, and if I try to start the file inside it tells me

Code: Select all

MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
Could not find ScummVM window for retrieving default display mode!
and does not start. I do not know if there is any context between this 3 mesa-messages and the not starting game (the older 1.9 from repository gives me the same 3 errors atm but is still starting fine) or the bus-access-error in Mandelbulbers OpenCL-renderer...maybe you have an idea.
The MESA errors in combination with the previous error message sounds like something (e.g. some wrongly compiled OpenCL kernel) screwed up the GPU or its kernel driver. In this case, restarting the Raspberry Pi will remedy the problem.

In short:
The VC4CL implementation could be responsible for screwing up graphics related programs (which, if you can reproduce the error, I will investigate). But these kinds of errors should be remedied with a reboot.

Micha1982
Posts: 261
Joined: Wed Oct 03, 2012 11:18 am

Re: OpenCL on the VideoCore IV!

Thu Apr 12, 2018 4:58 am

I was wrong, these "MESA-LOADER: failed to retrieve device information" also occurs before installing your driver.
Whyever...but I start a new thread to find out
Alles, was schiefgehen kann, wird auch schiefgehen.

User avatar
Gavinmc42
Posts: 2108
Joined: Wed Aug 28, 2013 3:31 am

Re: OpenCL on the VideoCore IV!

Mon Apr 23, 2018 3:09 am

I got ARM's Compute Library to compile on Gentoo64 on the weekend.
Er Sakaki, got it to compile and then showed me how to do it :oops:
Hint, go headless ;)

One of the Compute Lib compile options is Opencl=0.
Perhaps that could change soon/now?
ARM use the Mali GPU for OpenCL, so the Lib would need to be forked?

Not all of OpenCL will work but how much is needed for ARM Compute Lib?

Gentoo64 ships with GCC 7.3.0 and LLVM6, not sure if that helps?

To make maximum use of the PI3B+ CPU's power for Machine Learning type apps, using both Aarch64 and GPU would be nice.
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

vottghern
Posts: 1
Joined: Wed Aug 15, 2018 10:26 am

Re: OpenCL on the VideoCore IV!

Wed Aug 15, 2018 10:35 am

Hello!

I'm trying with OpenCV 4.0.0-pre with T-API on Raspberry Pi 3 B. This is code:

Code: Select all

import cv2
 
img = cv2.UMat(cv2.imread("image.jpg", cv2.IMREAD_COLOR))
imgUMat = cv2.UMat(img)
gray = cv2.cvtColor(imgUMat, cv2.COLOR_BGR2GRAY)
gray = cv2.GaussianBlur(gray, (7, 7), 1.5)
gray = cv2.Canny(gray, 0, 50)
 
cv2.imshow("edges", gray)
cv2.waitKey();
Result without sudo:

Code: Select all

python3 ./app2.py 
[VC4CL] can't open /dev/mem
[VC4CL] This program should be run as root. Try prefixing command with: sudo
The image is displayed after 2 seconds

Result WITH sudo:

Code: Select all

sudo python3 ./app2.py 
[ WARN:0] Can't save OpenCL binary into cache: /root/.cache/opencv/4.0-pre/opencl_cache/32-bit--Broadcom--VideoCore_IV_GPU--0_4/imgproc--color_rgb_23843c9b6cac3e766b305aa2dc124bc1.bin
OpenCV(4.0.0-pre) /home/pi/ocv_src/opencv-master/modules/core/src/ocl.cpp:3767: error: (-220:Unknown error code -220) OpenCL error CL_INVALID_VALUE (-30) during call: clGetProgramInfo(handle, CL_PROGRAM_BINARIES, sizeof(ptr), &ptr, NULL) in function 'getProgramBinary'

[ WARN:0] Can't save OpenCL binary into cache: /root/.cache/opencv/4.0-pre/opencl_cache/32-bit--Broadcom--VideoCore_IV_GPU--0_4/imgproc--canny_2e3c93ad703f4bcee1efbbcc0107fc8d.bin
OpenCV(4.0.0-pre) /home/pi/ocv_src/opencv-master/modules/core/src/ocl.cpp:3767: error: (-220:Unknown error code -220) OpenCL error CL_INVALID_VALUE (-30) during call: clGetProgramInfo(handle, CL_PROGRAM_BINARIES, sizeof(ptr), &ptr, NULL) in function 'getProgramBinary'

OpenCL error CL_INVALID_WORK_GROUP_SIZE (-54) during call: clEnqueueNDRangeKernel('stage1_with_sobel', dims=2, globalsize=368x246x1, localsize=16x1x1) sync=false
terminate called without an active exception
The image is displayed after 28 seconds

This can somehow be fixed?

Return to “Graphics programming”

Who is online

Users browsing this forum: No registered users and 1 guest