Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-08-11 Thread Keith Whitwell
On Wed, 2010-07-21 at 18:53 -0700, Ian Romanick wrote: > One of the items on the TODO list is proper support for GLSL ES. That > work won't happen until the last couple weeks of August, so I don't > think any sort of ES testing is suitable merge criteria. Unless, of > course, the tests in questi

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-28 Thread Brian Paul
On 07/23/2010 02:04 PM, Eric Anholt wrote: On Thu, 22 Jul 2010 08:01:30 -0600, Brian Paul wrote: On 07/21/2010 07:53 PM, Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As everyone knows, a group of us at Intel have been rewriting Mesa's GLSL compiler. The work started out-

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-23 Thread Eric Anholt
On Thu, 22 Jul 2010 08:01:30 -0600, Brian Paul wrote: > On 07/21/2010 07:53 PM, Ian Romanick wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > As everyone knows, a group of us at Intel have been rewriting Mesa's > > GLSL compiler. The work started out-of-tree as a stand alone c

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-23 Thread Zack Rusin
On Wednesday 21 July 2010 21:53:28 Ian Romanick wrote: > We have developed our own set of merge requirements, and these are > listed below. Since this is such a large subsystem, we want to solicit > input from the other stakeholders. > > * No piglit regressions, except draw_buffers-05.vert, comp

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-22 Thread Tom Stellard
On Wed, Jul 21, 2010 at 06:53:28PM -0700, Ian Romanick wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > As everyone knows, a group of us at Intel have been rewriting Mesa's > GLSL compiler. The work started out-of-tree as a stand alone compiler. > We moved all of our work to the glsl

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-22 Thread Tom Stellard
On Thu, Jul 22, 2010 at 06:34:43PM +1000, Dave Airlie wrote: > On Thu, Jul 22, 2010 at 11:53 AM, Ian Romanick wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > As everyone knows, a group of us at Intel have been rewriting Mesa's > > GLSL compiler.  The work started out-of-tree a

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-22 Thread Brian Paul
On 07/21/2010 07:53 PM, Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As everyone knows, a group of us at Intel have been rewriting Mesa's GLSL compiler. The work started out-of-tree as a stand alone compiler. We moved all of our work to the glsl2 branch in the Mesa tree a

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-22 Thread Dave Airlie
On Thu, Jul 22, 2010 at 11:53 AM, Ian Romanick wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > As everyone knows, a group of us at Intel have been rewriting Mesa's > GLSL compiler.  The work started out-of-tree as a stand alone compiler. >  We moved all of our work to the glsl2 branch

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-22 Thread Michel Dänzer
On Mit, 2010-07-21 at 18:53 -0700, Ian Romanick wrote: > > We haven't and, for all practical purposes, can't test with Gallium [...] Testing with softpipe/llvmpipe is basically the same as with swrast, either via swrastg_dri.so or standalone libGL. If you guys have problems setting that up, we'r

Re: [Mesa-dev] Merge criteria for glsl2 branch

2010-07-21 Thread Corbin Simpson
I personally do not care about Gallium breakage as long as the classic drivers do not break. This is because any Gallium breakage in that case would necessarily be from Gallium bugs, which I'd rather find sooner than later. Posting from a mobile, pardon my terseness. ~ C. On Jul 21, 2010 6:58 PM,

[Mesa-dev] Merge criteria for glsl2 branch

2010-07-21 Thread Ian Romanick
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As everyone knows, a group of us at Intel have been rewriting Mesa's GLSL compiler. The work started out-of-tree as a stand alone compiler. We moved all of our work to the glsl2 branch in the Mesa tree as soon as we had some actual code being generat