From: Dave Airlie
If the geom shader emits a point size we failed to find it here,
use the correct API to look it up.
Fixes:
tests/spec/glsl-1.50/execution/geometry/point-size-out.shader_test
---
src/gallium/auxiliary/draw/draw_pipe_wide_point.c | 9 +
1 file changed, 1 insertion(+), 8
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/midgard/midgard_nir_algebraic.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/drivers/panfrost/midgard/midgard_nir_algebraic.py
b/src/gallium/drivers/panfrost/midgard/midgard_nir_algebraic.py
ind
Although this is not functional (and the command stream side is not
aiming for ES3 right now), this is enough to run dEQP-GLES3 shader
tests with the version override directive; this is useful, as some ES3
shader feature can occur in ES2 class shaders due to lowering.
Signed-off-by: Alyssa Rosenzw
On Midgard, float ops support standard source modifiers (abs/neg) and
destination modifiers (sat/pos/round). Integer ops do not support these,
however. To cope, we use native NIR source modifiers for floats, but
lower them away to iabs/ineg for integers, implementing those ops
simultaneously to avo
From: Dave Airlie
With indirect rendering it's fine to set the instance count
parameter to 0, and expect the rendering to be ignored.
Fixes assert in KHR-GLES31.core.compute_shader.pipeline-gen-draw-commands
on softpipe
v2: return earlier before changing fpstate
---
src/gallium/auxiliary/draw/
From: Dave Airlie
With indirect rendering it's fine to set the instance count
parameter to 0, and expect the rendering to be ignored.
Fixes assert in KHR-GLES31.core.compute_shader.pipeline-gen-draw-commands
on softpipe
---
src/gallium/auxiliary/draw/draw_pt.c | 4 +++-
1 file changed, 3 insert
Signed-off-by: Alyssa Rosenzweig
---
.../drivers/panfrost/midgard/midgard.h| 29 +++
1 file changed, 29 insertions(+)
diff --git a/src/gallium/drivers/panfrost/midgard/midgard.h
b/src/gallium/drivers/panfrost/midgard/midgard.h
index f3cabff8c2f..c40c94bc378 100644
--- a/
Fixes
dEQP-GLES2.functional.shaders.conversions.scalar_to_scalar.bool_to_int_fragment
Signed-off-by: Alyssa Rosenzweig
---
.../panfrost/midgard/midgard_compile.c| 48 ---
1 file changed, 30 insertions(+), 18 deletions(-)
diff --git a/src/gallium/drivers/panfrost/midgard/
Fixes dEQP-GLES2.functional.shaders.linkage.varying_type_vec2 (among
many others).
Signed-off-by: Alyssa Rosenzweig
---
.../panfrost/midgard/midgard_compile.c| 43 ++-
1 file changed, 23 insertions(+), 20 deletions(-)
diff --git a/src/gallium/drivers/panfrost/midgard/mid
Fixes
dEQP-GLES2.functional.shader.conversions.scalar_to_scalar.int_to_bool_vertex
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/midgard/midgard_compile.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/panfrost/midgard/midgard_compile.c
b/src/gallium
Fixes
dEQP-GLES2.functional.shaders.swizzles.vector_swizzles.mediump_bvec2_x_vertex
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/midgard/midgard_compile.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/src/gallium/drivers/panfrost/midgard/midgard_compile.c
b/src
Some of these are not yet fully functional due to related bugs, but this
the correct op mapping. The native ball/bany opcodes act on vec4's
unconditionally. That said, both ball and bany have the nice property
that duplicating an argument does not affect their output, so the
default "hanging swizzl
Our viewport code hardcoded a number of wrong assumptions, which sort of
sometimes worked but was definitely wrong (and broke most of dEQP). This
corrects the logic, accounting for flipped-Y framebuffers, which
fixes... most of dEQP.
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfr
This preliminary implementation should handle some basic cases. Future
work should scissor the FRAGMENT job as well for efficiency.
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/pan_context.c | 22 --
1 file changed, 16 insertions(+), 6 deletions(-)
diff
Though they output scalars, they need a vector unit to make sense.
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/midgard/helpers.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/gallium/drivers/panfrost/midgard/helpers.h
b/src/gallium/drivers
Fixes a bunch of crashes in dEQP-GLES2.functional.buffer.*
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/pan_context.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/src/gallium/drivers/panfrost/pan_context.c
b/src/gallium/drivers/pan
Fixes issues in most of dEQP-GLES2.functional.shaders.*
Signed-off-by: Alyssa Rosenzweig
---
.../drivers/panfrost/midgard/midgard_compile.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/src/gallium/drivers/panfrost/midgard/midgard_compile.c
b/src/gallium
Whereas a normal fcsel acts on a boolean input in r31.w, the fcsel_i
variant acts on an integer input in r31.w, which can be preloaded with
an instruction like imov (with the appropriate negate flag on the
source).
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/midgard/helpers
https://bugs.freedesktop.org/show_bug.cgi?id=99781
--- Comment #15 from Hal Gentz ---
https://lists.freedesktop.org/archives/mesa-dev/2019-March/217153.html
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug._
From 7a701d9839ff788a79519d6ff310b489d4c1376e Mon Sep 17 00:00:00 2001
From: Hal Gentz
Date: Sun, 24 Mar 2019 16:52:39 -0600
Subject: [PATCH] Fixes assertion fail on startup in
`glXCreateContextAttribsARB`.
To quote Uli Schlacher, who understands this stuff more than I do:
> The function __gl
https://bugs.freedesktop.org/show_bug.cgi?id=99781
--- Comment #14 from Hal Gentz ---
Created attachment 143767
--> https://bugs.freedesktop.org/attachment.cgi?id=143767&action=edit
Patch that fixes bug.
Hey,
This patch fixes this bug. I had to also patch `__glXSendErrorForXcb` because
`glXCr
Please ignore this patch. Somehow my emails are getting delayed.
This is just a duplicate of the other patch which is on mailing list.
On 3/24/19 10:19 AM, Sagar Ghuge wrote:
> From: Sagar Ghuge
>
> Print quad value same as unsigned quad so that we can distinguish in
> between quater control d
https://bugs.freedesktop.org/show_bug.cgi?id=110230
--- Comment #3 from Laurent ---
But the link is not correct, this gives me an url not found error :
https://www.mesa3d.org/doxygen/main/index.html
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=110230
Bug ID: 110230
Summary: error while generating the source code documentation
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110230
--- Comment #2 from Laurent ---
Ah this is something I have to install apart.
Ok I've installed doxygen and now it worked.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99781
--- Comment #13 from Uli Schlachter ---
Created attachment 143766
--> https://bugs.freedesktop.org/attachment.cgi?id=143766&action=edit
A single-threaded reproducer
I think I came up with a single-threaded program reproducing the bug. More
det
https://bugs.freedesktop.org/show_bug.cgi?id=110230
--- Comment #4 from Andre Klapper ---
If some incorrect link is given somewhere please explain where that incorrect
link is given.
Nobody can fix something without clear steps to reproduce...
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=99781
Hal Gentz changed:
What|Removed |Added
Attachment #143763|0 |1
is obsolete|
Print quad value same as unsigned quad so that we can distinguish in
between quater control disassembled values for e.g 1/2/3[Q] and
immediate quad value for e.g 1Q. This allows round-tripping through the
assembler/disassembler.
Signed-off-by: Sagar Ghuge
---
src/intel/compiler/brw_disasm.c | 2
https://bugs.freedesktop.org/show_bug.cgi?id=99781
Uli Schlachter changed:
What|Removed |Added
CC||psyc...@znc.in
--
You are receiving th
https://bugs.freedesktop.org/show_bug.cgi?id=110230
Andre Klapper changed:
What|Removed |Added
Summary|error while generating the |"Read the documentation
https://bugs.freedesktop.org/show_bug.cgi?id=110230
Andre Klapper changed:
What|Removed |Added
CC||a9016...@gmx.de
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110230
--- Comment #5 from Laurent ---
Here :
https://www.mesa3d.org/sourcedocs.html
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-de
https://bugs.freedesktop.org/show_bug.cgi?id=99781
--- Comment #12 from Uli Schlachter ---
I took a look at this and I would guess that the bug is in mesa. However, I do
not want to built mesa myself and thus I will not test my theory.
The function __glXSendError() in mesa's src/glx/glx_error.c
https://bugs.freedesktop.org/show_bug.cgi?id=99781
Hal Gentz changed:
What|Removed |Added
CC||zegen...@protonmail.com
--- Comment #8 from
This patch refactors a substantial amount of code in preparation for
mipmaps. In particular, we know have a correct slice abstraction based
on offsets; cpu/gpu are no longer arbitrary pointers. We additionally
shuffle around other code to accompany these changes and cleanup how
tiled textures are h
This code is probably a wholesale duplication of the corresponding code
in mesa/src/vbo/vbo_minmax_indices.c; we should investigate reusing
that.
Signed-off-by: Alyssa Rosenzweig
---
src/gallium/drivers/panfrost/pan_context.c | 108 ++--
src/gallium/drivers/panfrost/pan_resource
https://bugs.freedesktop.org/show_bug.cgi?id=99781
--- Comment #11 from Hal Gentz ---
Created attachment 143765
--> https://bugs.freedesktop.org/attachment.cgi?id=143765&action=edit
Patch for printing out backtraces for possibly relevant functions.
--
You are receiving this mail because:
You
Looks good to me.
Reviewed-by: Neha Bhende
Regards,
Neha
From: mesa-dev on behalf of Brian Paul
Sent: Friday, March 22, 2019 12:51 PM
To: mesa-dev@lists.freedesktop.org
Cc: Neha Bhende
Subject: [Mesa-dev] [PATCH] st/mesa: fix texture deletion context
Looks good to me.
Reviewed-by: Jose Fonseca
Though I wonder if this could happen also when not destroying the current
context. (Ie, if we need zoombie textures too?)
Jose
From: Brian Paul
Sent: Friday, March 22, 2019 19:51
To: mesa-dev@lists.freedesktop.org
41 matches
Mail list logo
