On Friday 11 December 2009 08:05:24 michal wrote: > > There's gs_instance_id which specifies the id of the instance of the > > geometry shader (which is different than the global draw instance). > > There's also the number of vertices that the geometry shader works on (1 > > points, 2 lines, 3 triangles, 6 triangle adjacency etc) (which although > > is a readable variable in glsl, is something that is encoded in D3D by > > the way of encoding the input primitive in the shader). (plus of course > > there are the properties of the shader e.g. input primitive, output > > primitive and max number of vertices that it emits). > > > > What Keith is referring though is the fact that our input layout is going > > to be a bit difficult because for geometry shader it's > > DCL SV[0].x, PRIMITIVE_ID > > DCL SV[1].y, GS_INSTANCE_ID > > DCL IN[0][0..n], POSITION > > DCL IN[1][0..n], COLOR > > so whether you have SV or not is not the issue, it's the fact that we > > have different dimensional inputs that is not ideal. Right now I don't > > really see a way of getting rid of that. > > And I agree with that. Since you provided more SV examples that make > sense (though GS_INSTANCE_ID is something SM5 introduces), you should > stick with SYSTEM_VALUE register file. There is nothing gross about > having INPUT registers two-dimensional, and SYSTEM_VALUE one-dimensional.
k, it seems we're all on the same page then. Just to reiterate what we'll provide is a) PROPERTY token that takes a property name and then has a few unsigned worth of data e.g. PROPERTY GS_INPUT_PRIMITIVE TRIANGLES PROPERTY GS_MAX_VERTICES 32 PROPERTY COMPUTE_THREADS 4 4 4 b) a new SV register file that is used for system generated variables that are injected in the pipeline, plus some additional semantics e.g. DCL SV[0], VERTEX_ID DCL SV[0], PRIMITIVE_ID DCL SV[0], FACE of those two likely only the latter is a bit unclear since basically all other low level languages do it via another form of a DCL token. imho though the new register file is semantically clearer and if it proves that a new DCL token is in fact better suited for this it's not like we're committed to a lifetime tgsi token compatibility and we'll be able to simply change it. i provide a patch over the weekend for both, the quicker we'll have this the quicker we'll be able to judge its actual viability. 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
