Jerome Glisse wrote on 2010-03-11 18:13:
> Hi all,
>
> I have been a little bit out of the loop on the mesa side, thus now i am
> having a bunch of questions relating to gallium, apologies if i am asking
> for obvious thing.
>
> First in tgsi compiler there is a Dimension field (struct tgsi_dimension)
> that i don't understand, it seems all driver are ignoring it, from quick
> glimpse to tgsi code it's for 2d array addressing, but i think glsl only
> talks about 1d array. What are the exepction for this field ? Should
> driver care ?
>
>
It makes sense for geometry shaders, where you use one dimension to
address input vertex, and another one to index a particular input
attribute within that vertex.
> What is the indirect boolean for in src or dst operand of an instruction ?
> What is the GLSL equivalent of it.
>
>
This is used to e.g. address constant registers with a non-constant index.
> A more practical question are what are the gallium branches likely to be
> merge in the next few weeks ? I will likely have r600g driver in good
> shape enough in the next few weeks to consider merging it with master
> but i would like first to port it to the lastest gallium change before
> merging it so i don't put the burden on people working on those
> branches.
>
> What are the plan to expand TGSI to support new shader feature ? (double
> precision op, ...
I am planning to add a new set of texture fetch/sampler instructions in
the immediate future. The gallium-double-opcodes branch has stalled,
though, so it won't be merged any time soon.
|
