https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #51 from pavi...@yahoo.fr ---
I'm on Fedora 22 x64 with Nouveau and I have this tooltip corruption in
Chromium too. I hope that can be fixed.
Thank you
--
You are receiving this mail because:
You are the QA Contact for the bug.
You
From: Marek Olšák
For debugging, bug reports, etc.
This is not in the radeonsi directory, but it is about radeonsi.
---
src/gallium/drivers/radeon/r600_pipe_common.c | 2 ++
src/gallium/drivers/radeon/r600_pipe_common.h | 2 ++
src/gallium/drivers/radeon/r600_texture.c
From: Marek Olšák
---
src/gallium/drivers/radeonsi/si_state.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/src/gallium/drivers/radeonsi/si_state.c
b/src/gallium/drivers/radeonsi/si_state.c
index 384c8e2..c87f661 100644
---
From: Marek Olšák
---
src/gallium/drivers/radeon/r600_texture.c | 2 +-
src/gallium/drivers/radeonsi/cik_sdma.c | 2 +-
src/gallium/drivers/radeonsi/si_blit.c| 6 +++---
src/gallium/drivers/radeonsi/si_dma.c | 2 +-
src/gallium/drivers/radeonsi/si_state.c | 4
Signed-off-by: Rob Clark
---
src/glsl/Makefile.sources |1 +
src/glsl/nir/nir.c|8 +
src/glsl/nir/nir.h|2 +
src/glsl/nir/nir_clone.c | 1012 +
4 files changed, 1023 insertions(+)
create mode
From: Rob Clark
Mostly the implementation of nir_shader_clone() for copying a NIR
shader IR, plus couple cleanups, reference counting, and helper
macros. The reference counting will be useful for mesa-st (and
perhaps other state trackers), since there are cases when
From: Rob Clark
Convenient place to put in some extra sanity checking, without making
things messy for the drivers running the passes.
TODO: convert ir3/vc4..
Signed-off-by: Rob Clark
---
src/glsl/nir/nir.h | 33 ++
From: Rob Clark
Add it to the private interface, since we'll need it for nir_clone().
Signed-off-by: Rob Clark
---
src/glsl/nir/nir.c | 13 +++--
src/glsl/nir/nir.h | 2 ++
From: Rob Clark
For gallium, at least, we'll need this to manage shader's lifetimes,
since in some cases both the driver and the state tracker will need
to hold on to a reference for variant managing.
Use nir_shader_mutable() before doing any IR opt/lowering/etc, to
The various cf nodes all get allocated w/ shader as their ralloc_parent,
so lets make this more explicit. Plus couple other corrections/
clarifications.
Signed-off-by: Rob Clark
---
src/glsl/nir/nir.c | 18 +-
src/glsl/nir/nir.h | 10 +-
2
From: Rob Clark
This will simplify things somewhat in clone.
Signed-off-by: Rob Clark
---
src/glsl/nir/glsl_to_nir.cpp | 6 ++
src/glsl/nir/nir.h | 11 +++
2 files changed, 17 insertions(+)
diff --git
Otherwise, passing -1 gets you:
error: invalid conversion from 'int' to 'nir_variable_mode' [-fpermissive]
Signed-off-by: Rob Clark
---
src/glsl/nir/nir.c | 4
src/glsl/nir/nir.h | 1 +
src/glsl/nir/nir_lower_io.c | 2 +-
On 23.10.2015 23:26, srol...@vmware.com wrote:
From: Roland Scheidegger
f16c intrinsic can only be emitted when AVX is used. So when we disable AVX
due to forcing 128bit vectors we must not use this intrinsic (depending on
llvm version, this worked previously because llvm
With the remark on patch 2 (radeonsi: properly check if DCC is enabled
and allocated), the series is
Reviewed-by: Nicolai Hähnle
On 24.10.2015 17:49, Marek Olšák wrote:
From: Marek Olšák
---
src/gallium/drivers/radeonsi/si_state.c | 10
On 24.10.2015 17:49, Marek Olšák wrote:
From: Marek Olšák
---
src/gallium/drivers/radeon/r600_texture.c | 2 +-
src/gallium/drivers/radeonsi/cik_sdma.c | 2 +-
src/gallium/drivers/radeonsi/si_blit.c| 6 +++---
src/gallium/drivers/radeonsi/si_dma.c | 2 +-
---
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 3 ---
1 file changed, 3 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vec4_generator.cpp
b/src/mesa/drivers/dri/i965/brw_vec4_generator.cpp
index d50184a..cd8eb0e 100644
--- a/src/mesa/drivers/dri/i965/brw_vec4_generator.cpp
+++
---
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 8
1 file changed, 8 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_vec4_generator.cpp
b/src/mesa/drivers/dri/i965/brw_vec4_generator.cpp
index 6569d81..d50184a 100644
--- a/src/mesa/drivers/dri/i965/brw_vec4_generator.cpp
Some constants (like 1.0 and 0.5) could be inlined as immediate inputs
without using their literal value. The r600_bytecode_special_constants()
function emulates the negative of these constants by using NEG modifier.
However some shaders define -1.0 constant and want to use it as 1.0.
They do so
Nice. All four are
Reviewed-by: Matt Turner
I'll send two trivial clean ups as well.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
When a TCS is present, the TES input gl_PatchVerticesIn is actually a
constant - it's simply the # of output vertices specified by the TCS
layout qualifiers. So, we can replace the system value with a constant,
which may allow further optimization, and will likely be more efficient.
If the TCS
20 matches
Mail list logo