On Mon, 2009-12-14 at 06:23 -0800, michal wrote: > To fully support geometry shaders, we need some means to declare a > two-dimensional register file. The following declaration > > DCL IN[3][0] > > would declare an input register with index 0 (first dimension) and size > 3 (second dimension). Since the second dimension is a size, not an index > (or, for that matter, an index range), a new token has been added that > specifies the declared size of the register.
Is this a good representation? What would happen if there was: DCL IN[4][0] DCL IN[3][1] Presumably the "3" is always going to be "3", and it's a property of the geometry shader - I think Zack has a patch which adds something like: PROP GS_VERTICES_IN 3 Then couldn't we just have the equivalent of: DCL IN[][0] DCL IN[][1] with the size of the first dimension specified by the property? Are there going to be cases where this doesn't work? Keith ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
