On Wednesday 09 December 2009 20:30:56 Igor Oliveira wrote:
> Hi Zack,
>
> 1) agreed. OpencCL is a complete different project and should exist in
> a different repository.
> 1.1) Well use Gallium as CPU backend is a software dilemma:
> "All problems in computer science can be solved by another level of
> indirection...except for the problem of too many layers of
> indirection"
> But in my opinion we can use Gallium for CPU operations too, using
> gallium as a backend for all device types we maintain a code
> consistency.
Yes, it will certainly make the code a lot cleaner. I think using llvmpipe we
might be able to get it working fairly quickly. I'll need to finish a few
features in Gallium3d first. In particular we'll need to figure out how to
handle memory hierarchies, i.e. private/shared/global memory accesses in
shaders. Then we'll have some basic tgsi stuff like scatter reads and writes to
structured buffers, types in tgsi (int{8-64}, float, double}, barrier and
memory
barrier instructions, atomic reduction instructions, performance events and
likely trap/breakpoint instructions.
We'll be getting all those fixed within the next few weeks.
z
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
