[Mesa3d-dev] Gallium questions ...
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 ? What is the indirect boolean for in src or dst operand of an instruction ? What is the GLSL equivalent of it. 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). 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#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
Re: [Mesa3d-dev] Gallium questions ...
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. -- 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
Re: [Mesa3d-dev] Gallium questions ...
On Thu, Mar 11, 2010 at 9:13 AM, Jerome Glisse gli...@freedesktop.org wrote: 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). Yeah, welcome to TGSI. You'll have to do like r300g and recompile the shader. -- Only fools are easily impressed by what is only barely beyond their reach. ~ Unknown Corbin Simpson mostawesomed...@gmail.com -- 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
