https://bugs.freedesktop.org/show_bug.cgi?id=97003
Timothy Arceri changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
From: "J Karanje, Kedar"
The feature is enabled by default during make however we need to
add the following to drirc to enable the feature at runtime.
vbo: Main algorithm & code to check for MVP & vertex position location
Build Files: Flags to enable BBOX Code and check AVX version
compiler: Co
On Fri, Aug 31, 2018 at 1:57 AM Dave Airlie wrote:
>
> From: Dave Airlie
>
> ac_surface.c: gfx6_compute_surface says
> /* DB doesn't support linear layouts. */
I think r100 was the last chip to support linear depth surfaces.
Alex
>
> Now if we expose linear depth and create a linear depth imag
From: Dave Airlie
ac_surface.c: gfx6_compute_surface says
/* DB doesn't support linear layouts. */
Now if we expose linear depth and create a linear depth image
and use CmdCopyImage to copy into it, we can't map the underlying
memory and read it linearly which I think should work.
---
src/amd/v
Reviewed-by: Marek Olšák
Marek
On Thu, Aug 30, 2018 at 7:29 PM, Dave Airlie wrote:
> From: Dave Airlie
>
> I have piglit results from my machine, but I must have messed up,
> and not built mesa in between properly.
>
> Fixes: bb17ae49ee2 (gallivm: allow to pass two swizzles into fetches.)
> --
Reviewed-by: Marek Olšák
Marek
On Thu, Aug 30, 2018 at 8:13 PM, Dave Airlie wrote:
> From: Dave Airlie
>
> This fixes:
> tests/spec/arb_enhanced_layouts/execution/component-layout/vs-fs-array-dvec3.shader_test
> since I reworked the 64-bit swizzles.
>
> Fixes: bb17ae49ee2 (gallivm: allow to pa
Sadly, there are no tests for this.
Marek
On Thu, Aug 30, 2018 at 6:24 PM, Ian Romanick wrote:
> This patch is
>
> Reviewed-by: Ian Romanick
>
> Is there a piglit test? I wonder how many other glDeleteFoo functions
> mishandle the id=0 case. :(
>
> On 08/30/2018 12:16 PM, Marek Olšák wrote:
>>
Assuming it all has no CTS regressions, and GTAV works.
Reviewed-by: Dave Airlie for the series.
On Thu, 30 Aug 2018 at 18:59, Samuel Pitoiset wrote:
>
> Never used.
>
> Signed-off-by: Samuel Pitoiset
> ---
> src/amd/vulkan/radv_nir_to_llvm.c | 6 --
> 1 file changed, 6 deletions(-)
>
> di
https://bugs.freedesktop.org/show_bug.cgi?id=54805
Timothy Arceri changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Fri., 31 Aug. 2018, 01:22 Michel Dänzer, wrote:
>
> On 2018-08-27 11:16 p.m., Dave Airlie wrote:
> > From: Dave Airlie
> >
> > This hijacks the top 16-bits of swizzle, to pass in the swizzle
> > for the second channel.
> >
> > This fixes handling .yx swizzles of 64-bit values.
> >
> > This sho
From: Dave Airlie
This fixes:
tests/spec/arb_enhanced_layouts/execution/component-layout/vs-fs-array-dvec3.shader_test
since I reworked the 64-bit swizzles.
Fixes: bb17ae49ee2 (gallivm: allow to pass two swizzles into fetches.)
---
src/gallium/drivers/radeonsi/si_shader_tgsi_setup.c | 7 +--
Previously, we had two field in shader_info: double_inputs_read and
double_inputs. Presumably, the one was for all double inputs that are
read and the other is all that exist. However, because nir_gather_info
regenerates these two values, there is a possibility, if a variable gets
deleted, that t
https://bugs.freedesktop.org/show_bug.cgi?id=107670
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #8 from Timothy A
https://bugs.freedesktop.org/show_bug.cgi?id=107457
Bug 107457 depends on bug 106865, which changed state.
Bug 106865 Summary: [GLK] piglit.spec.ext_framebuffer_multisample.accuracy
stencil tests fail
https://bugs.freedesktop.org/show_bug.cgi?id=106865
What|Removed
https://bugs.freedesktop.org/show_bug.cgi?id=106156
Bug 106156 depends on bug 106865, which changed state.
Bug 106865 Summary: [GLK] piglit.spec.ext_framebuffer_multisample.accuracy
stencil tests fail
https://bugs.freedesktop.org/show_bug.cgi?id=106865
What|Removed
On Thu, Aug 30, 2018 at 02:37:40PM -0700, Kenneth Graunke wrote:
> On Wednesday, August 29, 2018 1:38:51 PM PDT Nanley Chery wrote:
> > According to internal docs, some gen9 platforms have a pixel shader push
> > constant synchronization issue. Although not listed among said
> > platforms, this iss
From: Dave Airlie
I have piglit results from my machine, but I must have messed up,
and not built mesa in between properly.
Fixes: bb17ae49ee2 (gallivm: allow to pass two swizzles into fetches.)
---
src/gallium/drivers/radeonsi/si_shader.c | 13 -
1 file changed, 8 insertions(+), 5
This patch is
Reviewed-by: Ian Romanick
Is there a piglit test? I wonder how many other glDeleteFoo functions
mishandle the id=0 case. :(
On 08/30/2018 12:16 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> This fixes a firefox crash.
>
> Fixes: 781a78914c798dc64005b37c6ca1224ce06803fc
> ---
Many new platforms got added to gen_device_name_to_pci_device_id()
but the error message inside aubinator didn't reflected those
changes. So syncing on the same order to be sure that we are not
missing any now.
Cc: Anuj Phogat
Cc: Matt Turner
Cc: Jordan Justen
Signed-off-by: Rodrigo Vivi
---
Whiskey Lake uses the same gen graphics as Coffe Lake, including some
ids that were previously marked as reserved on Coffe Lake, but that
now are moved to WHL page.
This follows the ids and approach used on kernel's commit
b9be78531d27 ("drm/i915/whl: Introducing Whiskey Lake platform")
Cc: José
Amber Lake uses the same gen graphics as Kaby Lake, including a id
that were previously marked as reserved on Kaby Lake, but that
now is moved to AML page.
This follows the ids and approach used on kernel's commit
e364672477a1 ("drm/i915/aml: Introducing Amber Lake platform")
Reported-by: Timo Aa
On Wednesday, August 29, 2018 1:38:51 PM PDT Nanley Chery wrote:
> According to internal docs, some gen9 platforms have a pixel shader push
> constant synchronization issue. Although not listed among said
> platforms, this issue seems to be present on the GeminiLake 2x6's we've
> tested.
>
> We co
https://bugs.freedesktop.org/show_bug.cgi?id=107765
Bug ID: 107765
Summary: [regression] Batman Arkham City crashes with DXVK
under wine
Product: Mesa
Version: 18.2
Hardware: Other
OS: All
Status
From: Marek Olšák
This fixes a firefox crash.
Fixes: 781a78914c798dc64005b37c6ca1224ce06803fc
---
src/mesa/main/arrayobj.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/mesa/main/arrayobj.c b/src/mesa/main/arrayobj.c
index a23031fe182..6e0665c0e5d 100644
--- a/src/mesa/main/arrayo
Thanks!
On Thu, Aug 30, 2018 at 1:41 PM Caio Marcelo de Oliveira Filho <
caio.olive...@intel.com> wrote:
> Jason Ekstrand writes:
>
> > This fixes the GL_ARB_fragment_shader_interlock piglit test on gen8
> > platforms where the lack of metadata dirtying was causing another pass
> > to accidental
Jason Ekstrand writes:
> This fixes the GL_ARB_fragment_shader_interlock piglit test on gen8
> platforms where the lack of metadata dirtying was causing another pass
> to accidentally delete a much needed loop.
>
> Cc: Kenneth Graunke
> https://bugs.freedesktop.org/show_bug.cgi?id=107745
> Fixes
This fixes the GL_ARB_fragment_shader_interlock piglit test on gen8
platforms where the lack of metadata dirtying was causing another pass
to accidentally delete a much needed loop.
Cc: Kenneth Graunke
https://bugs.freedesktop.org/show_bug.cgi?id=107745
Fixes: 37f7983bcca1 "intel/compiler: Do ima
On Thu, Aug 30, 2018 at 03:40:16PM +0200, Erik Faye-Lund wrote:
> This moves the evergreen-specific max-sizes out as a driver-cap, so
> other drivers with less strict requirements also can use hw-atomics.
>
> Remove ssbo_atomic as it's no longer needed.
>
> We should now be able to use hw-atomics
On Thu, Aug 30, 2018 at 03:40:15PM +0200, Erik Faye-Lund wrote:
> This gets rid of a r600 specific hack in the state-tracker, and prepares
> for other drivers to be able to use hw-atomics.
>
> While we're at it, clean up some indentation in the various drivers.
>
> Signed-off-by: Erik Faye-Lund
https://bugs.freedesktop.org/show_bug.cgi?id=107457
Bug 107457 depends on bug 107223, which changed state.
Bug 107223 Summary: [GEN9+] 50% perf drop in SynMark Fill* tests (E2E RBC gets
disabled?)
https://bugs.freedesktop.org/show_bug.cgi?id=107223
What|Removed
From: Emil Velikov
The pipe_loader_release API closes the fd given, even if the pipe-loader
should _not_ take ownership of it.
With earlier commit we fixed pipe_loader_drm_probe_fd, and now with
cover the final piece.
Note that unlike the DRM case, here the caller _did_ forget to dup
before usi
Reported by Coverity: data is heap-allocated, but only freed in the
info->index_size != 0 branch.
CID: 1438238
Signed-off-by: Ernestas Kulik
---
src/gallium/auxiliary/util/u_vbuf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/auxiliary/util/u_vbuf.c
b/src/gallium/auxiliary/ut
Reported by Coverity: in the case where there exist hardware and
non-hardware queries, the code does not jump to err_free_query and leaks
the query.
CID: 1430194
Signed-off-by: Ernestas Kulik
---
src/gallium/drivers/vc4/vc4_query.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
Reported by Coverity: in the case of unsupported modifier request, the
code does not jump to the “fail” label to destroy the acquired resource.
CID: 1435704
Signed-off-by: Ernestas Kulik
---
src/gallium/drivers/v3d/v3d_resource.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch series takes care of several reported resource leaks.
Ernestas Kulik (4):
glsl_to_tgsi: Fix potential leak
u_vbuf: Fix leak
v3d: Fix leak
vc4: Fix leak
src/gallium/auxiliary/util/u_vbuf.c| 1 +
src/gallium/drivers/v3d/v3d_resource.c | 2 +-
src/gallium/drivers/vc4/
Reported by Coverity: arr_live_ranges is freed in a different branch
than the one in which it was allocated.
CID: 1438391
Signed-off-by: Ernestas Kulik
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/mesa/state_tracker
On 30/08/2018 16:23, Dylan Baker wrote:
Quoting Lionel Landwerlin (2018-08-30 06:58:39)
On 28/08/2018 17:01, Dylan Baker wrote:
Quoting Lionel Landwerlin (2018-08-28 02:39:58)
Yes, I think so. You asked on another commit too, both are related and
this depends on other commits from Jason.
Here
Quoting Tapani Pälli (2018-08-29 21:26:08)
>
>
> On 08/29/2018 06:22 PM, Dylan Baker wrote:
> > Quoting Tapani Pälli (2018-08-27 04:46:37)
> >> OpenGL ES spec states:
> >> "For normalized fixed-point rendering surfaces, the combination format
> >> RGBA and type UNSIGNED_BYTE is accepted.
Quoting Lionel Landwerlin (2018-08-30 06:42:06)
> Newer blit tests are enabling depth&stencils blits. We currently don't
> support it but can do by iterating over the aspects masks (copy some
> logic from the CopyImage function).
>
> Signed-off-by: Lionel Landwerlin
> Fixes: 9f44745eca0e41 ("anv:
Quoting Lionel Landwerlin (2018-08-30 06:58:39)
> On 28/08/2018 17:01, Dylan Baker wrote:
> > Quoting Lionel Landwerlin (2018-08-28 02:39:58)
> >> Yes, I think so. You asked on another commit too, both are related and
> >> this depends on other commits from Jason.
> >>
> >> Here is a list in order
On more recent HW, the indirect writes via the GGTT are internally
buffered presenting a nuisance to trying to use them for persistent
client maps. (We cannot guarantee that any write by the client will
then be visible to either the GPU or third parties in a timely manner,
leading to corruption.) F
On 2018-08-27 11:16 p.m., Dave Airlie wrote:
> From: Dave Airlie
>
> This hijacks the top 16-bits of swizzle, to pass in the swizzle
> for the second channel.
>
> This fixes handling .yx swizzles of 64-bit values.
>
> This should fixup radeonsi and llvmpipe.
>
> Bugzilla: https://bugs.freedesk
Due to having 2 additional RCs for 18.2.
Cc: Dylan Baker
Cc: Juan A. Suarez
Cc: Emil Velikov
Signed-off-by: Andres Gomez
---
docs/release-calendar.html | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/docs/release-calendar.html b/docs/release-calendar.html
index
On 30 August 2018 at 11:41, Eric Engestrom wrote:
> On Thursday, 2018-08-30 17:55:14 +0900, Tomasz Figa wrote:
>> Hi Erik, Emil, Eric,
>>
>> On Tue, Jul 10, 2018 at 12:41 AM Erik Faye-Lund wrote:
>> >
>> > On Thu, Jul 5, 2018 at 7:02 PM Emil Velikov
>> > wrote:
>> > >
>> > > On 5 July 2018 at 1
Hi Emil,
> Correct. We had a number of bugs (one of which breaking MT apps) that
> makes me cautious.
Working with environment variables basically is often asking for problems. The
thread race condition ones being the most prominent.
To overwrite something - especially for debugging - its ok to u
On 28/08/2018 17:01, Dylan Baker wrote:
Quoting Lionel Landwerlin (2018-08-28 02:39:58)
Yes, I think so. You asked on another commit too, both are related and
this depends on other commits from Jason.
Here is a list in order of cherry picking :
commit f430a37fa75f534c3a114b0ec546fa14f05f5da1
A
On 08/30/2018 07:32 AM, Eric Engestrom wrote:
On Thursday, 2018-08-30 11:12:11 +0100, Emil Velikov wrote:
From: Emil Velikov
The memory is allocated with the uppercase wrapper. Tear down should
match that.
You're right, in dri2_init_screen() / dri_kms_init_screen(), but looking
at the histor
Newer blit tests are enabling depth&stencils blits. We currently don't
support it but can do by iterating over the aspects masks (copy some
logic from the CopyImage function).
Signed-off-by: Lionel Landwerlin
Fixes: 9f44745eca0e41 ("anv: Use blorp to implement VkBlitImage")
Reviewed-by: Jason Eks
virgl_protocol.h is considered to have it's upstream in the
virglrenderer repository, and somehow these minor differences has
crept in.
Let's sync with the upstream to avoid this.
Signed-off-by: Erik Faye-Lund
---
src/gallium/drivers/virgl/virgl_protocol.h | 2 +-
1 file changed, 1 insertion(+)
From: Tomeu Vizoso
Emulating atomics on top of ssbos can lead to too small max SSBO count,
so let's use the hw-atomics mechanism to expose atomic buffers instead.
Signed-off-by: Erik Faye-Lund
---
src/gallium/drivers/virgl/virgl_context.c | 37 ++
src/gallium/drivers/virgl
This moves the evergreen-specific max-sizes out as a driver-cap, so
other drivers with less strict requirements also can use hw-atomics.
Remove ssbo_atomic as it's no longer needed.
We should now be able to use hw-atomics for some stages and not for
other, if needed.
Signed-off-by: Erik Faye-Lun
We're doing full c99 now, so there's no point in using the old boolean
type.
Signed-off-by: Erik Faye-Lund
---
This is not technically nessecary for the series, but IMO a nice cleanup
nevertheless.
src/mesa/state_tracker/st_extensions.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-
This gets rid of a r600 specific hack in the state-tracker, and prepares
for other drivers to be able to use hw-atomics.
While we're at it, clean up some indentation in the various drivers.
Signed-off-by: Erik Faye-Lund
---
src/gallium/drivers/etnaviv/etnaviv_screen.c | 3 +++
src/gallium/d
This makes the code a bit easier to follow; we first set up
MaxShaderStorageBlocks, then we either set up a dedicated
MaxAtomicBuffers, or we split MaxShaderStorageBlocks in two.
While we're at it, also make the SSBO-splitting code tolerate the
hypothetical case of having an odd number of SSBOs wi
MaxAtomicCounters has already been assigned in the loop above in the
ssbo_atomic = true case, so this will calculate the same value as the
default.
While we're at it, fixup indentation on the MaxAtomicBufferBindings
assign.
Signed-off-by: Erik Faye-Lund
---
src/mesa/state_tracker/st_extensions.
Here's a patch-series that cleans up some evergreen-specific gallium
assumptions regarding hw-atomic buffers, as well as uses them on virgl
to avoid reporting synthetically few SSBOs.
The goal is really for gallium drivers to accrately report the exact
amount of SSBOs and hw-atomic buffers they su
On Thursday, 2018-08-30 11:12:11 +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> The memory is allocated with the uppercase wrapper. Tear down should
> match that.
You're right, in dri2_init_screen() / dri_kms_init_screen(), but looking
at the history this used to be FREE() and Brian replace
On 30 August 2018 at 11:41, Juan A. Suarez Romero wrote:
> On Wed, 2018-08-29 at 14:16 +0100, Emil Velikov wrote:
>> On 29 August 2018 at 11:12, Juan A. Suarez Romero
>> wrote:
>> > Use scheduled pipelines to update both the base and the LLVM images.
>> >
>> > This way allows to have an updated
Hi Juan,
Something I should have mentioned ealier:
Pardon if my question are a bit rough - my rocker/docker experience is limited.
On 30 August 2018 at 11:22, Juan A. Suarez Romero wrote:
> On Wed, 2018-08-29 at 14:11 +0100, Emil Velikov wrote:
>> Hi Juan,
>>
>> I've shared a number of suggestio
On 30 August 2018 at 10:54, Mathias Fröhlich wrote:
> On Tuesday, 28 August 2018 16:22:33 CEST Emil Velikov wrote:
>> > From a higher point of view the approach looks good.
>> >
>> > To sum up, you basically associate an _EGLDevice with each _EGLDisplay
>> > where the _EGLDevice only contains the
If color buffer is locked, do not set its wayland buffer to NULL;
otherwise it can not be freed later.
Rather, flag it in order to destroy it later on the release event.
v2: instruct release event to unlock only or free wl_buffer too (Daniel)
This also fixes dEQP-EGL.functional.swap_buffers_with
okay, r-b with that.
On Thu, Aug 30, 2018 at 1:39 PM Samuel Pitoiset
wrote:
>
>
>
> On 8/30/18 12:30 PM, Bas Nieuwenhuizen wrote:
> > On Wed, Aug 29, 2018 at 10:55 PM Samuel Pitoiset
> > wrote:
> >>
> >> CTS doesn't test input clip/cull distances for the fragment
> >> shader stage, which explains
On 8/30/18 12:30 PM, Bas Nieuwenhuizen wrote:
On Wed, Aug 29, 2018 at 10:55 PM Samuel Pitoiset
wrote:
CTS doesn't test input clip/cull distances for the fragment
shader stage, which explains why this was totally broken. I
wrote a simple test locally that works now.
This fixes a crash with G
On Wed, 2018-08-29 at 14:16 +0100, Emil Velikov wrote:
> On 29 August 2018 at 11:12, Juan A. Suarez Romero wrote:
> > Use scheduled pipelines to update both the base and the LLVM images.
> >
> > This way allows to have an updated version of the base images even when
> > the respect Rockerfiles ke
On Thursday, 2018-08-30 17:55:14 +0900, Tomasz Figa wrote:
> Hi Erik, Emil, Eric,
>
> On Tue, Jul 10, 2018 at 12:41 AM Erik Faye-Lund wrote:
> >
> > On Thu, Jul 5, 2018 at 7:02 PM Emil Velikov
> > wrote:
> > >
> > > On 5 July 2018 at 17:17, Eric Engestrom wrote:
> > > > On Thursday, 2018-07-05
On Wed, Aug 29, 2018 at 10:55 PM Samuel Pitoiset
wrote:
>
> CTS doesn't test input clip/cull distances for the fragment
> shader stage, which explains why this was totally broken. I
> wrote a simple test locally that works now.
>
> This fixes a crash with GTA V and DXVK.
>
> Note that we are expor
On Wed, 2018-08-29 at 14:11 +0100, Emil Velikov wrote:
> Hi Juan,
>
> I've shared a number of suggestions. I'll leave that to you if they
> will be in v3 or patches on top.
>
> On 29 August 2018 at 11:12, Juan A. Suarez Romero wrote:
>
> > In order to build the images, Rocker is used. This is a
From: Emil Velikov
The memory is allocated with the uppercase wrapper. Tear down should
match that.
Cc: mesa-sta...@lists.freedesktop.org
Signed-off-by: Emil Velikov
---
src/gallium/state_trackers/dri/dri_screen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/gallium/
On Tuesday, 28 August 2018 16:22:33 CEST Emil Velikov wrote:
> > From a higher point of view the approach looks good.
> >
> > To sum up, you basically associate an _EGLDevice with each _EGLDisplay
> > where the _EGLDevice only contains the meta information where to
> > find the device and the _EGL
Fixes Vulkan CTS CL#2849. Similar to the ANV driver.
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_device.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
index 79dbbd886d..c300c88468 100644
--- a/src/amd/vulkan/radv
It's a special case because both are combined into a single array.
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_shader_info.c | 8
1 file changed, 8 insertions(+)
diff --git a/src/amd/vulkan/radv_shader_info.c
b/src/amd/vulkan/radv_shader_info.c
index 5925fd924c..6262acb1a6
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_nir_to_llvm.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/src/amd/vulkan/radv_nir_to_llvm.c
b/src/amd/vulkan/radv_nir_to_llvm.c
index 0c7b238e10..069fb53b68 100644
--- a/src/amd/vulkan/radv_nir_to_llvm.c
+++ b/sr
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_nir_to_llvm.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/src/amd/vulkan/radv_nir_to_llvm.c
b/src/amd/vulkan/radv_nir_to_llvm.c
index 069fb53b68..b2411fe38b 100644
--- a/src/amd/vulkan/radv_nir_to_llvm.c
+++ b/src/amd/vulkan/ra
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_nir_to_llvm.c | 49 +--
1 file changed, 40 insertions(+), 9 deletions(-)
diff --git a/src/amd/vulkan/radv_nir_to_llvm.c
b/src/amd/vulkan/radv_nir_to_llvm.c
index 17c76332e1..0c7b238e10 100644
--- a/src/amd/vulkan
The shader info pass takes care of this now.
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_nir_to_llvm.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/amd/vulkan/radv_nir_to_llvm.c
b/src/amd/vulkan/radv_nir_to_llvm.c
index d7cd8cc069..17c76332e1 100644
---
Never used.
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_nir_to_llvm.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/src/amd/vulkan/radv_nir_to_llvm.c
b/src/amd/vulkan/radv_nir_to_llvm.c
index b2411fe38b..af34c548c1 100644
--- a/src/amd/vulkan/radv_nir_to_llvm.c
+++ b/src/a
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_shader_info.c | 43 +++
1 file changed, 26 insertions(+), 17 deletions(-)
diff --git a/src/amd/vulkan/radv_shader_info.c
b/src/amd/vulkan/radv_shader_info.c
index a45c847c46..5925fd924c 100644
--- a/src/amd/vulka
Hi Erik, Emil, Eric,
On Tue, Jul 10, 2018 at 12:41 AM Erik Faye-Lund wrote:
>
> On Thu, Jul 5, 2018 at 7:02 PM Emil Velikov wrote:
> >
> > On 5 July 2018 at 17:17, Eric Engestrom wrote:
> > > On Thursday, 2018-07-05 14:43:02 +0100, Emil Velikov wrote:
> > >> On 5 July 2018 at 10:53, Eric Engest
On Thu, Aug 30, 2018 at 9:17 AM Samuel Pitoiset
wrote:
>
>
>
> On 8/30/18 2:49 AM, Jason Ekstrand wrote:
> > Now that image load/store intrinsics are variable-width, we need to set
> > num_components accordingly. In 15d39f474b890, both glsl_to_nir and
> > spirv_to_nir were updated to properly set
On 8/30/18 2:49 AM, Jason Ekstrand wrote:
Now that image load/store intrinsics are variable-width, we need to set
num_components accordingly. In 15d39f474b890, both glsl_to_nir and
spirv_to_nir were updated to properly set num_components but radv meta
was left behind.
Fixes: 15d39f474b890 "ni
80 matches
Mail list logo
