[Mesa-dev] [PATCH v2] nv50, nvc0: fix start_instance in manual push path

The start instance is applied as an offset into the buffer directly, ignoring the divisor, not as an instance id offset that respects the divisor. Signed-off-by: Ilia Mirkin Cc: "11.2 12.0" --- v1 -> v2: use translate's start_instance parameter. This relies on the earlier fix I just sent for s

[Mesa-dev] [PATCH] translate: fix start_instance parameter in sse version

The generic version gets this right already, but this was using an incorrect formula in SSE. Signed-off-by: Ilia Mirkin --- src/gallium/auxiliary/translate/translate_sse.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/src/gallium/auxiliary/translate/translate

[Mesa-dev] [PATCH] nvc0: don't make use of push hint if there are no non-const user vbos

This makes the check match up what we do on nv50 as well - there's no point in switching over the push path if everything's in managed buffers. This can happen when a shader uses a vertex without an enabled array - we end up passing it a constant attribute. This also has the effect of "fixing" som

[Mesa-dev] [PATCH] gallivm: don't use integer min/max sse intrinsics with llvm >= 3.9

From: Roland Scheidegger Apparently, these are deprecated. There's some AutoUpgrade feature which is supposed to promote these to cmp/select, which apparently doesn't work with jit code. It is possible it's not actually even meant to work (see the bug filed against llvm which couldn't provide an

[Mesa-dev] [PATCH] nv50, nvc0: fix start_instance in manual push path

The start instance is applied as an offset into the buffer directly, ignoring the divisor, not as an instance id offset that respects the divisor. Signed-off-by: Ilia Mirkin Cc: "11.2 12.0" --- src/gallium/drivers/nouveau/nv50/nv50_push.c | 10 +++--- src/gallium/drivers/nouveau/nv

Re: [Mesa-dev] [Mesa-stable] [PATCH 2/2] i965: Support "unlimited" compute shader scratch space.

Francisco Jerez writes: > Kenneth Graunke writes: > >> Ivybridge and Baytrail have a pretty harsh limit of 12kB scratch space >> per thread. However, we can exceed this limit with some clever tricks >> and gain effectively unlimited scratch space. >> >> Later platforms have a 2MB limit, which i

Re: [Mesa-dev] [Mesa-stable] [PATCH 2/2] i965: Support "unlimited" compute shader scratch space.

Kenneth Graunke writes: > Ivybridge and Baytrail have a pretty harsh limit of 12kB scratch space > per thread. However, we can exceed this limit with some clever tricks > and gain effectively unlimited scratch space. > > Later platforms have a 2MB limit, which is much more reasonable, but > we m

[Mesa-dev] [PATCH v2] gk104/ir: fix tex use generation to be more careful about eliding uses

If we have a loop, instructions before the tex might be added as tex uses, and those may in fact dominate all other uses of the tex results. This however doesn't mean that we don't need a texbar after the tex. Only check if uses dominate each other they are dominated by the tex. Bugzilla: https://

[Mesa-dev] [PATCH 19.5/64] isl/state: Don't set RenderTargetViewExtent for texture surfaces

The docs specify that this only matters for render targets and surfaces used with typed dataport messages. On some platforms (gen4-6) the Depth field has more bits than RenderTargetViewExtent so we can have textures with more levels than we can render to. Signed-off-by: Jason Ekstrand Cc: Chad V

[Mesa-dev] [PATCH] nir/algebraic: Remove imprecise flog2 optimizations

While mathematically correct, these two optimizations result in an expression with substantially lower precision than the original. For any positive finite floating-point value, log2(x) is well-defined and finite. More precisely, it is in the range [-150, 150] so any sum of logarithms log2(a) + lo

[Mesa-dev] [PATCH] gk104/ir: fix tex use generation to be more careful about eliding uses

If we have a loop, instructions before the tex might be added as tex uses, and those may in fact dominate all other uses of the tex results. This however doesn't mean that we don't need a texbar after the tex. Only check if uses dominate each other if they either both dominate the tex, or are both

Re: [Mesa-dev] [RFC 2/7] pipe-loader-drm: Add common pipe_screen refcounting

On Fri, Jun 17, 2016 at 12:51 PM, Ilia Mirkin wrote: > On Fri, Jun 17, 2016 at 1:45 PM, Rob Herring wrote: >> Some gallium drivers have implemented reference counting of pipe_screen >> to avoid creating multiple screens for a device. Move this into the >> pipe-loader where it can be shared. >> >>

Re: [Mesa-dev] [Mesa-stable] [PATCH] mapi: Export all GLES 3.1 functions in libGLESv2.so

On 18 June 2016 at 00:01, Kenneth Graunke wrote: > On Friday, June 17, 2016 5:58:21 PM PDT Ilia Mirkin wrote: >> On Fri, Jun 17, 2016 at 5:48 PM, Emil Velikov >> wrote: >> > On 17 June 2016 at 22:22, Jason Ekstrand wrote: >> >> On Fri, Jun 17, 2016 at 2:09 PM, Emil Velikov >> >> wrote: >> >>>

[Mesa-dev] [Bug 96358] SSO: wrong interface validation between GS and VS (regresion due to latest gles 3.1)

https://bugs.freedesktop.org/show_bug.cgi?id=96358 --- Comment #8 from gregory.hain...@gmail.com --- I did a quick of latest Ian's patches. They are working fine for me. Bug could be closed once there are merged. -- You are receiving this mail because: You are the QA Contact for the bug.

[Mesa-dev] [Bug 96573] Micro freezes resulting in crash

https://bugs.freedesktop.org/show_bug.cgi?id=96573 Bug ID: 96573 Summary: Micro freezes resulting in crash Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major