On 04/11/2014 10:29 PM, Matt Turner wrote:
> ---
> src/mesa/drivers/dri/i965/intel_debug.c | 1 +
> src/mesa/drivers/dri/i965/intel_debug.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/src/mesa/drivers/dri/i965/intel_debug.c
> b/src/mesa/drivers/dri/i965/intel_debug.c
> index dc742
On 04/11/2014 10:29 PM, Matt Turner wrote:
> ---
> src/mesa/drivers/dri/i965/brw_fs.cpp | 129
> +-
> src/mesa/drivers/dri/i965/brw_fs.h| 2 +
> src/mesa/drivers/dri/i965/brw_fs_reg_allocate.cpp | 2 +-
> src/mesa/drivers/dri/i965/brw_shader.cp
On 04/11/2014 10:29 PM, Matt Turner wrote:
> With INTEL_DEBUG=optimizer, write the output of dump_instructions() to a
> file each time an optimization pass makes progress. This lets you easily
> diff successive files to see what an optimization pass did.
>
> Example filenames written when running
On 04/11/2014 10:29 PM, Matt Turner wrote:
> Users will downcast if they don't have >32 debug flags.
> ---
> src/mesa/drivers/dri/common/utils.c | 7 +++
> src/mesa/drivers/dri/common/utils.h | 4 ++--
> 2 files changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/co
On Sun, Apr 13, 2014 at 12:12 AM, Kenneth Graunke wrote:
> On 04/11/2014 10:29 PM, Matt Turner wrote:
>> ---
>> src/mesa/drivers/dri/i965/brw_fs.cpp | 129
>> +-
>> src/mesa/drivers/dri/i965/brw_fs.h| 2 +
>> src/mesa/drivers/dri/i965/brw_fs_reg
On Sun, Apr 13, 2014 at 12:16 AM, Kenneth Graunke wrote:
> On 04/11/2014 10:29 PM, Matt Turner wrote:
>> With INTEL_DEBUG=optimizer, write the output of dump_instructions() to a
>> file each time an optimization pass makes progress. This lets you easily
>> diff successive files to see what an opti
For this series: Reviewed-by: Christian König
BTW: Can we get rid of RADEON_FLUSH_ASYNC and always flush
asynchronously? Just calling cs_sync_flush directly after the flush
should have the same effect as synchronous flushing.
Christian.
Am 12.04.2014 18:34, schrieb Marek Olšák:
From: Marek
On 04/13/2014 12:53 AM, Matt Turner wrote:
> On Sun, Apr 13, 2014 at 12:12 AM, Kenneth Graunke
> wrote:
>> On 04/11/2014 10:29 PM, Matt Turner wrote:
>>> ---
>>> src/mesa/drivers/dri/i965/brw_fs.cpp | 129
>>> +-
>>> src/mesa/drivers/dri/i965/brw_fs.h
From: Andreas Hartmetz
It is a better description of what goes on and it's shorter, too.
---
src/gallium/auxiliary/translate/translate_sse.c | 86 -
1 file changed, 43 insertions(+), 43 deletions(-)
diff --git a/src/gallium/auxiliary/translate/translate_sse.c
b/src/gall
From: Andreas Hartmetz
---
src/gallium/auxiliary/translate/translate_sse.c | 35 -
1 file changed, 28 insertions(+), 7 deletions(-)
diff --git a/src/gallium/auxiliary/translate/translate_sse.c
b/src/gallium/auxiliary/translate/translate_sse.c
index dace722..03d8276 1006
Hello, I noticed and incorrect uint->float conversion of vertex shader
input in an application I'm working on, so I set out to fix it.
In the meantime the application changed to avoid that conversion
because it seems broken in too many drivers.
So anyway, this series contains two actual bug fixes
From: Andreas Hartmetz
---
src/gallium/auxiliary/translate/translate_sse.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/src/gallium/auxiliary/translate/translate_sse.c
b/src/gallium/auxiliary/translate/translate_sse.c
index ca02b7a..992c5f6 100644
--- a/src/gallium/auxiliary/translate/t
From: Andreas Hartmetz
The only loss of precision here due to intrinsic properties of
unsigned int and float.
---
src/gallium/auxiliary/translate/translate_sse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/auxiliary/translate/translate_sse.c
b/src/gallium/aux
From: Andreas Hartmetz
It is possible that there are multiple input buffers but only one is
relevant for translation. Then there will be only a single translation
group, which might need to source data from a buffer index != 0.
Fixes wrong vertex shader inputs as observed while debugging with an
From: Andreas Hartmetz
---
src/gallium/auxiliary/translate/translate_sse.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/gallium/auxiliary/translate/translate_sse.c
b/src/gallium/auxiliary/translate/translate_sse.c
index 1b698cd..24d8017 100644
--- a/src/gallium/auxiliary/trans
From: Andreas Hartmetz
---
src/gallium/auxiliary/translate/translate_sse.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/gallium/auxiliary/translate/translate_sse.c
b/src/gallium/auxiliary/translate/translate_sse.c
index e25d450..8dd30c4 100644
--- a/src/gallium/
We originally thought that GL 3.0 required GL_DEPTH_COMPONENT16 to map
exactly to Z16. However, we misread the specification, thanks in part
to LaTeX reordering the tables in the PDF.
Page 180 of the GL 3.0 specification (glspec30.20080923.pdf) says:
"[...] memory allocation per texture component
We've learned a few things since we originally disabled Z16; this attempts
to summarize the issue. I am no expert on this subject, though, so the
comment may not be totally accurate.
I did some benchmarking on GM45 and Ironlake, and discovered that for
GLBenchmark 2.7 EgyptHD, using Z16 was 3% sl
Both are
Reviewed-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
19 matches
Mail list logo