-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like most of the bugs on the tracker have been fixed. The
remaining bugs are:
Bug 27831 - [regression] DynamicBranching3 does not render correctly:
I've been looking into this, but I haven't made much progress. I don't
know that it will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Romanick wrote:
Ian Romanick wrote:
Ian Romanick wrote:
So... what are our collective criteria for a 7.9 release to happen?
Paraphrasing the discussion a bit, it sounds like the only thing in the
way of a release is fixing a bunch of bugs.
On Tue, Sep 14, 2010 at 6:02 PM, Ian Romanick i...@freedesktop.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Romanick wrote:
Ian Romanick wrote:
Ian Romanick wrote:
So... what are our collective criteria for a 7.9 release to happen?
Paraphrasing the discussion a bit, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Romanick wrote:
Ian Romanick wrote:
So... what are our collective criteria for a 7.9 release to happen?
Paraphrasing the discussion a bit, it sounds like the only thing in the
way of a release is fixing a bunch of bugs. It sounds like there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Romanick wrote:
So... what are our collective criteria for a 7.9 release to happen?
Paraphrasing the discussion a bit, it sounds like the only thing in the
way of a release is fixing a bunch of bugs. It sounds like there are a
couple that are
The nv30/nv40 driver expects that all optimizations that can be
performed on TGSI without target knowledge to have already been
performed.
This seems a sensible principle in general to avoid drivers duplicating work.
In particular, registers are expected to be optimally allocated.
Doing this in
On Fri, Sep 3, 2010 at 12:54 AM, Dave Airlie airl...@gmail.com wrote:
- Later Radeons and NV chips: I thought that these each had their own
register allocators than ran after Mesa's. These should be able to do
the right thing. Yes?
r600c doesn't have anything smart for register
On Fri, Sep 3, 2010 at 10:46 AM, Marek Olšák mar...@gmail.com wrote:
On Fri, Sep 3, 2010 at 12:54 AM, Dave Airlie airl...@gmail.com wrote:
- Later Radeons and NV chips: I thought that these each had their own
register allocators than ran after Mesa's. These should be able to do
the
On Tue, 31 Aug 2010 19:35:09 -0600, Brian Paul bri...@vmware.com wrote:
On 08/31/2010 02:57 PM, Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
So... what are our collective criteria for a 7.9 release to happen?
Ian, I'm still getting up to speed on the new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian Paul wrote:
Ian, I'm still getting up to speed on the new compiler, but it looks
like a full 4-element temp/const vector is allocated for each GLSL
float. The previous compiler would try to pack four floats into a
single vector whenever
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We'd still like to release Mesa 7.9 at the end of September. That's
four weeks from now. As soon as the glsl2-loops branch lands (I'm
expecting this to be this week), all of the major development on the new
compiler will be complete. There's still
On Wed, Sep 1, 2010 at 6:57 AM, Ian Romanick i...@freedesktop.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We'd still like to release Mesa 7.9 at the end of September. That's
four weeks from now. As soon as the glsl2-loops branch lands (I'm
expecting this to be this week), all
On 08/31/2010 02:57 PM, Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We'd still like to release Mesa 7.9 at the end of September. That's
four weeks from now. As soon as the glsl2-loops branch lands (I'm
expecting this to be this week), all of the major development on the
13 matches
Mail list logo
