As long as there's no regressions in llvmpipe, looks great to me.
Am 29.03.19 um 06:48 schrieb Dave Airlie:
> This enables the ARB_gpu_shader5 vertex streams on softpipe.
>
> Signed-off-by: Dave Airlie
> ---
> src/gallium/drivers/softpipe/sp_screen.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On 3/29/19 1:54 PM, Brian Paul wrote:
> On 03/29/2019 12:58 PM, Ian Romanick wrote:
>> On 3/29/19 9:57 AM, Brian Paul wrote:
>>> __builtin_types_compatible_p() is GCC-specific and breaks the
>>> MSVC build.
>>>
>>> This intrinsic has been in u_vector_foreach() for a long time, but
>>> that macro
On 03/29/2019 12:58 PM, Ian Romanick wrote:
On 3/29/19 9:57 AM, Brian Paul wrote:
__builtin_types_compatible_p() is GCC-specific and breaks the
MSVC build.
This intrinsic has been in u_vector_foreach() for a long time, but
that macro has only recently been used in code
https://bugs.freedesktop.org/show_bug.cgi?id=109646
bmil...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=109646
--- Comment #9 from jam...@amd.com ---
Hi Bruno,
Please help verify the two new patches to address the issues that you found
during Chromium hardware acceleration enabled playback.
Thanks!
James Zhu
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=109646
--- Comment #8 from jam...@amd.com ---
Created attachment 143810
--> https://bugs.freedesktop.org/attachment.cgi?id=143810=edit
patch for blank issue fix
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are
https://bugs.freedesktop.org/show_bug.cgi?id=109646
jam...@amd.com changed:
What|Removed |Added
CC||jam...@amd.com
--- Comment #7 from
Build mesa 10592 completed
Commit 9987a3d448 by Karol Herbst on 3/28/2019 10:50 PM:
nir/print: fix printing the image_array intrinsic index\n\nFixes: 0de003be0363 ("nir: Add handle/index-based image intrinsics")\n\nSigned-off-by: Karol Herbst \nReviewed-by:
On 3/29/19 9:57 AM, Brian Paul wrote:
> __builtin_types_compatible_p() is GCC-specific and breaks the
> MSVC build.
>
> This intrinsic has been in u_vector_foreach() for a long time, but
> that macro has only recently been used in code
> (nir/nir_opt_comparison_pre.c) that's built with MSVC.
>
>
Looks good
Reviewed-by: Jose Fonseca
From: Brian Paul
Sent: Friday, March 29, 2019 16:57
To: mesa-dev@lists.freedesktop.org
Cc: Ian Romanick; Jose Fonseca; Neha Bhende
Subject: [PATCH] util: no-op __builtin_types_compatible_p() for non-GCC
compilers
__builtin_types_compatible_p() is GCC-specific and breaks the
MSVC build.
This intrinsic has been in u_vector_foreach() for a long time, but
that macro has only recently been used in code
(nir/nir_opt_comparison_pre.c) that's built with MSVC.
Fixes: 2cf59861a ("nir: Add partial redundancy
Without that kmscube with GALLIUM_TRACE would segfault like:
#0 0x in ()
#1 0x8f311760 in dri2_create_fence_fd (_ctx=0xe266b8b0, fd=10)
at ../src/gallium/state_trackers/dri/dri_helpers.c:122
#2 0x90788670 in dri2_create_sync (drv=0xe2667910,
This Patch is Acked-by: James Zhu
On 2019-03-28 9:08 a.m., Liu, Leo wrote:
> The number of render targets could be more than max of references,
> so we search the full list of the render pictures for the current
> render target index
>
> https://bugs.freedesktop.org/show_bug.cgi?id=109648
>
>
Hi,
On Wed, Mar 27, 2019 at 12:22:57PM +0100, Lucas Stach wrote:
> The context is self synchronizing at the GPU side, as commands are
> executed in order. We must not flush our own context when updating the
> resource use, as that leads to excessive flushing on effectively every
> draw call,
https://bugs.freedesktop.org/show_bug.cgi?id=109805
--- Comment #14 from rainbowsforthe...@gmail.com
---
(In reply to Samuel Pitoiset from comment #13)
> Are you able to reproduce the VM faults with mesa 19.0?
With Mesa 19.0.1, LLVM 8.0.0, Kernel 5.0.5 and Proton 4.2-1, it seems as though
The
On Fri, 29 Mar 2019 at 02:48, Alyssa Rosenzweig wrote:
>
> Fixes crash in dEQP-GLES2.functional.buffer.*
>
> Signed-off-by: Alyssa Rosenzweig
> ---
> src/gallium/drivers/panfrost/pan_context.c | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git
From the OpenGL 4.60.5 spec, section 4.4.1 Input Layout Qualifiers,
Page 67, (Location aliasing):
" Further, when location aliasing, the aliases sharing the location
must have the same underlying numerical type and bit
width (floating-point or integer, 32-bit versus 64-bit, etc.) and
https://bugs.freedesktop.org/show_bug.cgi?id=110261
--- Comment #3 from Denis ---
hi, I am able to reproduce this issue on Manjaro OS and intel (CFL CPU), with
system (18.3.4) and built from git mesa versions.
Can I provide some additional information for you to help in debugging?
Core was
On Thu, 2019-03-28 at 16:21 +0100, Samuel Pitoiset wrote:
> On 3/25/19 8:16 AM, Samuel Iglesias Gonsálvez wrote:
> > On Fri, 2019-03-22 at 17:21 +0100, Samuel Pitoiset wrote:
> > > Does this fix anything known?
> > >
> > I am writing CTS tests for VK_EXT_host_query_reset extension and I
> > found
https://bugs.freedesktop.org/show_bug.cgi?id=110268
--- Comment #3 from Samuel Pitoiset ---
We should be able to enable it but I have to deal with some failures first.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the
Reviewed-by: Timothy Arceri
On 29/3/19 6:39 pm, Samuel Pitoiset wrote:
This fixes the following piglit with RadeonSI
tests/spec/arb_gpu_shader_fp64/execution/built-in-functions/fs-frexp-dvec4.shader_test
Signed-off-by: Samuel Pitoiset
---
src/amd/common/ac_llvm_build.c | 2 +-
1 file
This fixes the following piglit with RadeonSI
tests/spec/arb_gpu_shader_fp64/execution/built-in-functions/fs-frexp-dvec4.shader_test
Signed-off-by: Samuel Pitoiset
---
src/amd/common/ac_llvm_build.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=110259
Samuel Pitoiset changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
23 matches
Mail list logo
