Sorry, forgot to reply-all ...
-------- Original Message --------
Subject: Re: [Mesa3d-dev] Gallium questions ...
Date: Thu, 11 Mar 2010 18:29:10 +0100
From: Christoph Bumiller <e0425...@student.tuwien.ac.at>
To: Jerome Glisse <gli...@freedesktop.org>
On 11.03.2010 18:13, Jerome Glisse wrote:
> 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 ?
>
>
In geometry programs you have 2D arrays, Dimension specifying
the vertex index (nv50 does use this);
at least that's how I interpreted it (left out the swizzles):
MOV OUT[0], IN[a[i] + j][b[k] + n]
i = src->DimIndirect.Index
j = src->Dimension.Index
k = src->Indirect.Index
n = src->Register.Index
a = src->DimIndirect.File
b = src->Indirect.File
VertexID = a[i] + j
> What is the indirect boolean for in src or dst operand of an instruction ?
> What is the GLSL equivalent of it.
>
>
If src->Register.Indirect is true, src->Indirect is the addressing
register to be used.
> Also i think GLSL state that the sampler information should be defined
> at shader build time but the TGSI doesn't seems to provide those, for
> r600 i need to have a shader rewritting because of this (it's not big
> and i don't mind much and i also can avoid rewritting by checking if
> there is a change in the bound sampler).
>
What sampler information ?
The texture target is defined in FullInstruction.Texture.Texture,
is that not sufficient ?
Christoph
> 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, ...)
>
>
> Thanks to who ever can shed some light on those question for me :)
>
> Cheers,
> Jerome
>
> ------------------------------------------------------------------------------
> Download Intel® 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
>
------------------------------------------------------------------------------
Download Intel® 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
