Let's track all different applications having issues with Clover and radeonsi/r600 here.
It would be easier to track the few apps which work, unfortunately :(
Not to forget my mandelbulber bug 82717.
It was actually working with funfunctor's partial image support found at https://cgit.freedesktop.org/~funfunctor/mesa/log/?h=clover-image-support-enabled
Currently it fails on llvm-svn 293174 with
OpenCL Build log: <unknown>:0:0: in function fractal3D void (%struct.sClPixel addrspace(1)*, %struct.sClInBuff addrspace(1)*, %struct.sClInConstants addrspace(2)*, %struct.sClReflect addrspace(1)*, %opencl.image2d_ro_t.0 addrspace(2)*, i32): unsupported call to function get_global_id
but since it's already been working with this non-mainlined code, it's one that can be crossed off the list maybe very soon already.
Thanks for contributing. Very glad to hear about Mandelbulber almost working. I have added it to  as well.
Sorry for asking, but the reason behind this bug report is because someone is finally willing to put some love into clover or nothing changed in that regard?
(In reply to darkbasic from comment #4)
> Sorry for asking, but the reason behind this bug report is because someone
> is finally willing to put some love into clover or nothing changed in that
I am planning to do that in the coming weeks/months/(decades/millennia), now that GROMACS finally works. I won't promise anything, but I would love to get at least CP2K and LAMMPS working (bug 99539 and bug 99540), which might help other applications as well.
Hopefully it will go a bit faster than it did with GROMACS now that I have grasped how different layers of the OpenCL stack work and how to fix bugs there.
Thanks, I would love to have at least Darktable working. With the CPU it takes 30+ seconds to process a single photo, compared to 0.5 seconds when using OpenCL.
(In reply to darkbasic from comment #6)
> Thanks, I would love to have at least Darktable working. With the CPU it
> takes 30+ seconds to process a single photo, compared to 0.5 seconds when
> using OpenCL.
If you are up for experimentation, the patches mentioned in comment #2 might be worth trying.
This is probably not the best place to mention it, but the GalliumCompute feature status matrix was last updated in June of 2015.
I imagine there have been improvements, including atomics fixes I've gotten merged to fix ImageMagick bugs I opened in the past year.
Could that perhaps be updated to reflect the current status? It might inspire other broken applications to try OpenCL again, and file bugs that could be more narrowly targeted.
I have beeing fishing through the Bugzilla backlog on Clover to see what's there. Most of the bugs are fixed by now, but a couple are still there. Sorry for bugspam.
clpeak - various symptoms over the past months but now a solid crash:
luxmark - crashes: http://www.luxrender.net/forum/viewtopic.php?f=16&t=13353
Any system where you have more than one OpenCL vendor using the same LLVM version: "CommandLine Error: Option 'enable-value-profiling' registered more than once!": https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852746
Blender Cycles OpenCL support also doesn't work.
(In reply to Luke A. Guest from comment #11)
> Blender Cycles OpenCL support also doesn't work.
Is there a bug filed in a bug tracker somewhere for this one?
Doesn't seem to be.
Jan Vesely is maintaining a table of test results: http://paul.rutgers.edu/~jv356/piglit/gcn-latest-3/problems.html
And an equivalent one for r600, sorry for double comment: http://paul.rutgers.edu/~jv356/piglit/radeon-latest-5/problems.html
Hi, any news on the OpenCL image support? I really miss darktable support.
Added a bug for darktable specifically: bug 107115
Here is a problem.
I updated LLVM-trunk and installed.
Than run this commands:
git clone http://llvm.org/git/libclc.git
More info: https://www.fieldengineer.com/blogs/new-jersey-field-engineer-the-innovation-of-engineering-workforce
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/135.