Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

On 17.12.2010 17:54, Marek Olšák wrote: > On Fri, Dec 17, 2010 at 4:32 PM, Brian Paul > wrote: > > Christoph, > > I don't see a patch for the st/mesa program translation code to check > that we don't exceed the limit. Were you going to take care of > that

Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

On Fri, Dec 17, 2010 at 4:32 PM, Brian Paul wrote: > Christoph, > > I don't see a patch for the st/mesa program translation code to check > that we don't exceed the limit. Were you doing to take care of that too? > > I guess we're assuming that the max number of generic inputs == max > number of

Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

Christoph, I don't see a patch for the st/mesa program translation code to check that we don't exceed the limit. Were you doing to take care of that too? I guess we're assuming that the max number of generic inputs == max number of generic outputs. I think that's OK until a counter case appe

Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

Christoph, This looks good. Thanks for bringing this back to life. Keith On Thu, 2010-12-16 at 07:47 -0800, Christoph Bumiller wrote: > On 12/14/2010 12:36 PM, Keith Whitwell wrote: > > On Mon, 2010-12-13 at 12:01 -0800, Christoph Bumiller wrote: > >> I want to warm this up again adding nvc0 an

Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

On 12/14/2010 12:36 PM, Keith Whitwell wrote: > On Mon, 2010-12-13 at 12:01 -0800, Christoph Bumiller wrote: >> I want to warm this up again adding nvc0 and >> GL_ARB_separate_shader_objects to the picture. >> >> The latter extends GL_EXT_separate_shader_objects to support user >> defined varyings

Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

On Mon, 2010-12-13 at 12:01 -0800, Christoph Bumiller wrote: > I want to warm this up again adding nvc0 and > GL_ARB_separate_shader_objects to the picture. > > The latter extends GL_EXT_separate_shader_objects to support user > defined varyings and guarantees well defined behaviour only if > - va

Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

I want to warm this up again adding nvc0 and GL_ARB_separate_shader_objects to the picture. The latter extends GL_EXT_separate_shader_objects to support user defined varyings and guarantees well defined behaviour only if - varyings are declared inside the gl_PerVertex/gl_PerFragment block the bloc

Re: [Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

On Tue, 2010-04-13 at 03:55 -0700, Luca Barbieri wrote: > Personally I think the simplest idea for now could be to have all > drivers support 256 indices or, in the case of r600 and svga, the > maximum value supported by the hardware, and expose that as a cap (as > well as another cap for the numbe

[Mesa3d-dev] [PATCH 0/6] [RFC] Formalization of the Gallium shader semantics linkage model

This patch series is intended to resolve the issue of semantic-based shader linkage in Gallium. It can also be found in the RFC-gallium-semantics branch. It does not change the current Gallium design, but rather formalizes some limitations to it, and provides infrastructure to implement this mod