https://bugs.freedesktop.org/show_bug.cgi?id=109396
Bug ID: 109396
Summary: [radeonsi, regression, bisected, d3d trace] NFS
Underground - 18.2.8 render fine, flickering present
in 18.3.2
Product: Mesa
Version: 18.
This MR implements the new VK_EXT_buffer_device_address extension. Part of
the reason why it's so many patches is that 21 of them are part of !70
(intel: Add support for split SEND instructions). Ignoring those, most of
the remaining patches are NIR or SPIR-V work to add support for the
**Physica
While you're at it, also copy precision. I think that's the only other
relevant bit. With that,
Reviewed-by: Ilia Mirkin
On Sat, Jan 19, 2019 at 6:58 PM Karol Herbst wrote:
>
> fixes a couple of deqp tests (on nvc0 and potential other drivers):
> dEQP-GLES3.functional.shaders.invariance.highp.c
fixes a couple of deqp tests (on nvc0 and potential other drivers):
dEQP-GLES3.functional.shaders.invariance.highp.common_subexpression_1
dEQP-GLES3.functional.shaders.invariance.highp.common_subexpression_2
dEQP-GLES3.functional.shaders.invariance.highp.common_subexpression_3
dEQP-GLES3.functional
Sorry for the wrong list. Sent again to piglit@.
On Sat, Jan 19, 2019 at 03:40:01PM -0800, Caio Marcelo de Oliveira Filho wrote:
> One extra character is leaking from the text into the copied line.
> The "+ 1" is an artifact from when malloc was used, strndup will add
> the extra '\0' after copyi
Reviewed-by: Ilia Mirkin
On Sat, Jan 19, 2019 at 6:34 PM Rhys Kidd wrote:
>
> Signed-off-by: Rhys Kidd
> ---
> src/gallium/drivers/nouveau/nv50/nv50_screen.c | 2 ++
> src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 2 ++
> 2 files changed, 4 insertions(+)
>
> diff --git a/src/gallium/drivers
One extra character is leaking from the text into the copied line.
The "+ 1" is an artifact from when malloc was used, strndup will add
the extra '\0' after copying text_size bytes (if available).
7c8ee3f0f "util: simplify string duplication logic"
---
tests/util/piglit-shader-test.c | 2 +-
1 fi
Signed-off-by: Rhys Kidd
---
src/gallium/drivers/nouveau/nv50/nv50_screen.c | 2 ++
src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 2 ++
2 files changed, 4 insertions(+)
diff --git a/src/gallium/drivers/nouveau/nv50/nv50_screen.c
b/src/gallium/drivers/nouveau/nv50/nv50_screen.c
index d83926f2
Hey,
I just discovered that meson hardcodes the list of llvm-config binary names to
try in mesonbuild/dependencies/dev.py, line 214ff ([0]). This is breaking now
since LLVM upstream switched to version 9 and branched version 8 of to become a
stable release soon. See [1] for the upstream ticket I fi
nouveau warns on unhandled pipe CAPs, including where they may be set by
u_pipe_screen_get_param_defaults()
This patch avoids spurious text in debug outputs, e.g. when running piglit.
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/133
Rhys
___
https://bugs.freedesktop.org/show_bug.cgi?id=109394
--- Comment #4 from tempel.jul...@gmail.com ---
Created attachment 143166
--> https://bugs.freedesktop.org/attachment.cgi?id=143166&action=edit
renderdoc capture part 4
--
You are receiving this mail because:
You are the QA Contact for the bu
https://bugs.freedesktop.org/show_bug.cgi?id=109394
--- Comment #3 from tempel.jul...@gmail.com ---
Created attachment 143164
--> https://bugs.freedesktop.org/attachment.cgi?id=143164&action=edit
renderdoc capture part 3
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=109394
--- Comment #2 from tempel.jul...@gmail.com ---
Created attachment 143163
--> https://bugs.freedesktop.org/attachment.cgi?id=143163&action=edit
renderdoc capture part 2
--
You are receiving this mail because:
You are the QA Contact for the bu
https://bugs.freedesktop.org/show_bug.cgi?id=109394
--- Comment #1 from tempel.jul...@gmail.com ---
Created attachment 143162
--> https://bugs.freedesktop.org/attachment.cgi?id=143162&action=edit
renderdoc capture part 1
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=109394
Bug ID: 109394
Summary: dark lines visual corruption in ground texture with
Heroes of the Storm DXVK
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS
Both the Intel and RADV people have been really bad about adding things
to the release notes. We should start actually paying attention.
---
docs/relnotes/19.0.0.html | 7 +++
1 file changed, 7 insertions(+)
diff --git a/docs/relnotes/19.0.0.html b/docs/relnotes/19.0.0.html
index 10c883f398f
---
src/intel/vulkan/anv_descriptor_set.c | 43 +++
1 file changed, 31 insertions(+), 12 deletions(-)
diff --git a/src/intel/vulkan/anv_descriptor_set.c
b/src/intel/vulkan/anv_descriptor_set.c
index a308fbf8540..a4e466cf3dd 100644
--- a/src/intel/vulkan/anv_descriptor_set
Thanks, pushed to master.
On 18/01/2019 18:09, Rafael Antognolli wrote:
Reviewed-by: Rafael Antognolli
On Fri, Jan 18, 2019 at 05:01:58PM +, Lionel Landwerlin wrote:
Doesn't save us a great deal of lines but at least they get decoded in
aubinators.
Signed-off-by: Lionel Landwerlin
---
s
https://bugs.freedesktop.org/show_bug.cgi?id=106151
--- Comment #31 from Bas Nieuwenhuizen ---
Moved the Mario Party issue to
https://bugs.freedesktop.org/show_bug.cgi?id=109393 . A priori I'd like to not
combine bugs based on the fact that it is a hang with the same GPU. These often
have differe
https://bugs.freedesktop.org/show_bug.cgi?id=109393
Bug ID: 109393
Summary: [vega10] hang with Mario Party 9 through Dolphin
Product: Mesa
Version: 18.3
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=106151
--- Comment #30 from Jaap Buurman ---
Still running into this issue, now while running Mario Party 9 through Dolphin.
This is a particularly good test case, because I can reliably get it to crash
in the main menu after seconds/minutes. This ONLY
Reviewed-by: Bas Nieuwenhuizen
On Sat, Jan 19, 2019 at 2:56 PM Rhys Perry wrote:
>
> It's common in some applications to bind a new graphics pipeline without
> ending up changing any context registers.
>
> This has a pipline have two command buffers: one for setting context
> registers and one f
On Sat, Jan 19, 2019 at 2:56 PM Rhys Perry wrote:
>
> Signed-off-by: Rhys Perry
> ---
> src/amd/vulkan/radv_cmd_buffer.c | 65
> src/amd/vulkan/radv_private.h| 2 +
> 2 files changed, 43 insertions(+), 24 deletions(-)
>
> diff --git a/src/amd/vulkan/radv_cmd
Signed-off-by: Rhys Perry
---
src/amd/vulkan/radv_cmd_buffer.c | 65
src/amd/vulkan/radv_private.h| 2 +
2 files changed, 43 insertions(+), 24 deletions(-)
diff --git a/src/amd/vulkan/radv_cmd_buffer.c b/src/amd/vulkan/radv_cmd_buffer.c
index f430b4f20dd..6d
Signed-off-by: Rhys Perry
---
src/amd/vulkan/radv_cmd_buffer.c | 118 +++
1 file changed, 58 insertions(+), 60 deletions(-)
diff --git a/src/amd/vulkan/radv_cmd_buffer.c b/src/amd/vulkan/radv_cmd_buffer.c
index f41d6c0b3e7..f430b4f20dd 100644
--- a/src/amd/vulkan/radv
It's common in some applications to bind a new graphics pipeline without
ending up changing any context registers.
This has a pipline have two command buffers: one for setting context
registers and one for everything else. The context register command buffer
is only emitted if it differs from the
26 matches
Mail list logo
