On Saturday 03 April 2010 18:58:36 Marek Olšák wrote:
> On Sun, Apr 4, 2010 at 12:10 AM, Zack Rusin
>  <za...@vmware.com<mailto:za...@vmware.com>> wrote: I thought the initial
>  proposal was likely a lot more feasible for a GSOC (of course there one
>  has to point out that Mesa's GLSL compiler already does unroll loops and
>  in general simplifies control-flow so the points #1 and #2 are largely
>  no-ops, but surely there's enough work on Gallium Radeon's drivers left to
>  keep Tom busy). Otherwise having a well-defined and reduced scope with
>  clear deliverables would be rather necessary for LLVM->TGSI code because
>  that is not something that you could get rock solid over a summer.
> 
> It doesn't seem to simplify branches or unroll loops that much, if at all.

It does for cases where the arguments are known.


>  It fails even for the simplest cases like this one:
> 
>     if (gl_Vertex.x < 30.0)

which is unknown at the compilation time.

z

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to