commit 26d86d26f9f972b19c7040bdb1b1daf48537ef3e added
gl_shader_program::UniformLocationBaseScale. According to the code
comments in that commit, UniformLocationBaseScale must be =1.
UniformLocationBaseScale is of type unsigned. Coverity reported a Macro
compares unsigned to 0 defect as well.
https://bugs.freedesktop.org/show_bug.cgi?id=64959
Quentin Sardem FF7 Glidic sardemff7+freedesk...@sardemff7.net changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=66149
Priority: medium
Bug ID: 66149
Assignee: mesa-dev@lists.freedesktop.org
Summary: [HSW] Background of application icon has garbage after
update kernelmesa in order to support Graphics
https://bugs.freedesktop.org/show_bug.cgi?id=66149
Chris Wilson ch...@chris-wilson.co.uk changed:
What|Removed |Added
Attachment #81397|text/plain |image/png
https://bugs.freedesktop.org/show_bug.cgi?id=66149
EvaWang evaw...@linpus.com changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=66149
--- Comment #1 from EvaWang evaw...@linpus.com ---
garbage shows when mouse move on the icon.
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
Am 25.06.2013 00:54, schrieb Zack Rusin:
Because our code couldn't handle it we were skipping rendering
if we detected overflows. According to the spec we should
still render but with all 0 vertices, which is what the llvm
code already does. So for the llvm paths lets enable processing
even
Some shells dose not set variables sequentially in a statement i.e. a=X
b=${a} won't set b to X but empty value.
This patch introduce ; to make sure mo is set properly before lang
assignment.
Cf. https://bugs.gentoo.org/show_bug.cgi?id=471302
---
src/mesa/drivers/dri/common/xmlpool/Makefile.am
Series looks good to me.
- Original Message -
Because our code couldn't handle it we were skipping rendering
if we detected overflows. According to the spec we should
still render but with all 0 vertices, which is what the llvm
code already does. So for the llvm paths lets enable
On 06/24/2013 11:02 PM, Vinson Lee wrote:
commit 26d86d26f9f972b19c7040bdb1b1daf48537ef3e added
gl_shader_program::UniformLocationBaseScale. According to the code
comments in that commit, UniformLocationBaseScale must be =1.
UniformLocationBaseScale is of type unsigned. Coverity reported a
I'm planning to release Mesa 9.1.4 next Monday (7/1). I'm going to pick
over a couple more fixes today and tomorrow, but there shouldn't be many
changes.
When I do this release, Carl Worth is going to look over my shoulder,
and he's planning to take over 9.1.x release management from me.
On 19 June 2013 19:45, Anuj Phogat anuj.pho...@gmail.com wrote:
Current implementation of ext_framebuffer_multisample_blit_scaled in
i965/blorp uses nearest filtering for multisample scaled blits. Using
nearest filtering produces blocky artifacts and negates the benefits
of MSAA. That is the
Ian Romanick i...@freedesktop.org writes:
From: Ian Romanick ian.d.roman...@intel.com
The checks to determine when the data can be uploaded in an interleaved
fashion can be tricked by certain data layouts. For example,
float data[...];
glVertexAttribPointer(0, 4, GL_FLOAT,
On 06/25/2013 11:57 AM, Eric Anholt wrote:
Ian Romanick i...@freedesktop.org writes:
From: Ian Romanick ian.d.roman...@intel.com
The checks to determine when the data can be uploaded in an interleaved
fashion can be tricked by certain data layouts. For example,
float data[...];
Ian Romanick i...@freedesktop.org writes:
On 06/25/2013 11:57 AM, Eric Anholt wrote:
Ian Romanick i...@freedesktop.org writes:
From: Ian Romanick ian.d.roman...@intel.com
The checks to determine when the data can be uploaded in an interleaved
fashion can be tricked by certain data layouts.
Kenneth Graunke kenn...@whitecape.org writes:
On 06/21/2013 10:57 AM, Eric Anholt wrote:
Batch dumping is now handled by shared code in libdrm.
---
src/mesa/drivers/dri/i915/Makefile.sources | 1 -
src/mesa/drivers/dri/i915/i915_debug.c | 843
-
We weren't taking into account the size of element
that is to be fetched, which meant that it was possible
to overflow the buffer reads if the stride was very
close to the end of the buffer, e.g. stride = 3, buffer
size = 4, and the element to be read = 4. This should
be properly detected as an
Our buffer overflow arithmetic was susceptible to integer
overflows which was the buffer overflow logic to break.
Lets use the llvm overflow intrinsics to check for integer
overflows while computing the stride/needed buffer size.
Signed-off-by: Zack Rusin za...@vmware.com
---
Integers could easily overflow is the starting instance
was large enough. Instead of letting bogus counts through
set the instance to max if it overflown and let our
regular buffer overflow computation handle it.
Signed-off-by: Zack Rusin za...@vmware.com
---
Hi,
This series improves clover's kernel argument handling by allowing drivers to
specify an alignment for the input buffer and also by sign/zero extending the
arguments when required. In order to test these patches on r600g and radeonsi,
you will need to also apply the LLVM patches which were
From: Tom Stellard thomas.stell...@amd.com
---
src/gallium/state_trackers/clover/core/kernel.cpp | 40 +++
src/gallium/state_trackers/clover/core/kernel.hpp | 10 +++---
2 files changed, 25 insertions(+), 25 deletions(-)
diff --git
From: Tom Stellard thomas.stell...@amd.com
This value for this CAP is the alignment to use when storing kernel
arguments in the input buffer.
---
src/gallium/docs/source/screen.rst| 13 +
src/gallium/drivers/r600/r600_pipe.c | 11 ++-
From: Tom Stellard thomas.stell...@amd.com
---
src/gallium/state_trackers/clover/core/kernel.cpp | 28 +--
src/gallium/state_trackers/clover/core/kernel.hpp | 5
2 files changed, 21 insertions(+), 12 deletions(-)
diff --git
From: Tom Stellard thomas.stell...@amd.com
---
src/gallium/state_trackers/clover/core/kernel.cpp | 23 +++---
src/gallium/state_trackers/clover/core/kernel.hpp | 4 +++-
src/gallium/state_trackers/clover/core/module.hpp | 10 +-
https://bugs.freedesktop.org/show_bug.cgi?id=66175
Priority: medium
Bug ID: 66175
Assignee: mesa-dev@lists.freedesktop.org
Summary: R600/SI: SETCC for v2i32/v4i32 triggers LLVM assertion
Severity: normal
Classification: Unclassified
From: Roland Scheidegger srol...@vmware.com
OpenGL doesn't support this but d3d10 does.
It is a bit of a pain as it is necessary to keep track of queries
still active at the end of a scene, which is also why I cheat a bit
and limit the amount of simultaneously active queries to (arbitrary)
16
From: Roland Scheidegger srol...@vmware.com
trivial, copied from llvmpipe
---
src/gallium/drivers/softpipe/sp_surface.c | 42 +++--
1 file changed, 40 insertions(+), 2 deletions(-)
diff --git a/src/gallium/drivers/softpipe/sp_surface.c
On Mon, Jun 24, 2013 at 1:53 AM, na...@elisp.net wrote:
Some shells dose not set variables sequentially in a statement i.e. a=X
b=${a} won't set b to X but empty value.
This patch introduce ; to make sure mo is set properly before lang
assignment.
Cf.
https://bugs.freedesktop.org/show_bug.cgi?id=66149
--- Comment #3 from EvaWang evaw...@linpus.com ---
When can we get 9.1.4 to try it? Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=66184
Priority: medium
Bug ID: 66184
Keywords: have-backtrace
Assignee: mesa-dev@lists.freedesktop.org
Summary: src/mesa/state_tracker/st_glsl_to_tgsi.cpp:3216:simpli
fy_cmp:
On Mon, Jun 24, 2013 at 2:13 PM, Christian König
deathsim...@vodafone.de wrote:
Am 24.06.2013 18:39, schrieb Ilia Mirkin:
On Mon, Jun 24, 2013 at 4:48 AM, Christian König
deathsim...@vodafone.de wrote:
Am 23.06.2013 18:59, schrieb Ilia Mirkin:
Signed-off-by: Ilia Mirkin
max_threads cannot be greater than 28. It is either 21 or 28.
Fixes Logically dead code defect reported by Coverity.
Signed-off-by: Vinson Lee v...@freedesktop.org
---
src/gallium/drivers/ilo/ilo_gpe_gen6.c |3 ---
1 file changed, 3 deletions(-)
diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=66149
--- Comment #4 from EvaWang evaw...@linpus.com ---
The issue can't be reproduced with 9.1 branch.
When will 9.1.4 release? Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
33 matches
Mail list logo
