Great to know, I already proposed the talk. Alex is already coming, are you planing on sending someone else too?
Originally Posted by bridgman
Alex is already *registered*, now we're trying to get travel approved
That's strange, the bigger the company, the higher the burden to do anything a bit "out of the ordinary". It always bothered me.
Originally Posted by bridgman
Anyway, I hope the travel gets approved.
Well, compute != graphics. The developer consensus on LLVM is that it's not well-suited for shaders, i.e. graphics. Compute is a different matter.
Originally Posted by smitty3268
If we're lucky, we can get Gallium driver developers to add LLVM IR support to their drivers, if someone comes up with a good way to code-generate for GPUs using LLVM. But I would guess that the LunarGLASS developers have already figured that part out. Or at least, I think they've figured out a way to code generate for targets that require structured control flow. I think they said a few months ago that they had gotten it working when targeting Mesa IR, which requires structured control flow like GPUs. So maybe some of their work can be adapted to Clover.
Here are more details about the status of Clover:
- The API is complete, that means that any application can now use Clover and will not fail due to missing or unimplemented symbols.
- The implementation in itself is complete: there are no stubs, and all the API actually does something.
- The interesting part: Clover can launch native kernels (Phoronix spoke about that two months ago), and compiled kernels. So, it is really feature-complete.
- The only thing missing are built-ins functions. It means that even if we can create memory objects, images, events, command queues and all the OpenCL objects, and that we can compile and launch OpenCL C kernels, these kernel cannot yet use functions like clamp(), smooth(), etc.
- The most complex built-ins are implemented though, like image reading and writing, and barrier() (a built-in that will be described in detail in the documentation as it uses things like POSIX contexts (man setcontext)).
I'll write the documentation in the following days (I already begun). It will be in Doxygen format, and I was pleased yesterday to see that Doxygen is now able to produce exceptionally good and beautiful documentation, in regards of what it produced one or two years ago. Then, I'll rework some part of the image functions (they are currently tied to the x86 architecture using SSE2, I will reimplement them in a more architecture-neutral way).
The documentation will be available in the source code and also on my people.freedesktop.org page, so anybody will be able to view it.
And another very important thing.
Is this going to be OpenCL 1.0 or 1.1?
Originally Posted by plonoma
Denis, that is some really nice work -- a *very* productive summer.
Originally Posted by steckdenis
So, let me see if I got this right...
Clover implements the complete OpenCL API and can execute OpenCL programs. But at the moment, all of it runs on the CPU, and getting it to actually run on GPUs will be a hitload of work and nobody really knows how it should be done.
And this is due to a few factors:
- the situation regarding IRs in Gallium is muddy: Mesa IR seems to be on the way out, with TGSI being generated directly, but there are attempts to use LLVM too, and GLSL IR is also in the mix
- TGSI is good for graphics (shaders), but is not good for computing, like OpenCL, which is why people are proposing LLVM
- LLVM sucks at graphics
So we're likely looking at (at least) two IRs coexisting: one for shaders, one for OpenCL stuff?
Just to say that the documentation I'm writing is available on http://people.freedesktop.org/~steck...ver/index.html . Sorry for the bad English (it is already a bit special in short messages, so I don't imagine in whole documentation pages), comments and corrections welcome.
This documentation will be expanded in the following days. I recommend to clone the Clover's git repository (http://cgit.freedesktop.org/~steckdenis/clover) and to build the documentation yourself, as Freedesktop.org uses a very outdated version of Doxygen and Dot. By using a modern distribution, you'll get a way more beautiful documentation (smoothed dot graphs, nicer page layout, logo, etc).
Tags for this Thread