https://bugs.freedesktop.org/show_bug.cgi?id=105068
--- Comment #5 from Pietro Pesci Feltri ---
I add the parameters manually pressing "e" in the grub menu 2 days ago. One
hour later the initialization process was not ended.
I was forced to reboot the machine.
Anyway thanks.
On 18-02-16 13:44:00, Antognolli, Rafael wrote:
"This field controls the granularity of the replay mechanism when
coming back into a previously preempted context."
The kernel disables this bit but whitelists the register, and it's a
context register. So enable it and take advantage of finer
On 16/02/18 21:07, Samuel Pitoiset wrote:
Vega stats should be:
Totals from affected shaders:
SGPRS: 106088 -> 106232 (0.14 %)
VGPRS: 74652 -> 74700 (0.06 %)
Spilled SGPRs: 692 -> 658 (-4.91 %)
Code Size: 2967708 -> 2953028 (-0.49 %) bytes
Max Waves: 18178 -> 18162 (-0.09 %)
My local
Kenneth Graunke writes:
> By default, 3DSTATE_CONSTANT_* Constant Buffer 0 is relative to dynamic
> state base address. This makes it unusable for pushing UBOs.
>
> There is a bit in the INSTPM register (or CS_DEBUG_MODE2 on Skylake)
> which controls whether buffer 0 is
Kenneth Graunke writes:
> Kernel 4.16 has proper context isolation, which means we can change
> the L3 configuration without worrying about that leaking to other
> newly created contexts, breaking the assumptions of other userspace.
>
> So, disable our workaround to
By default, 3DSTATE_CONSTANT_* Constant Buffer 0 is relative to dynamic
state base address. This makes it unusable for pushing UBOs.
There is a bit in the INSTPM register (or CS_DEBUG_MODE2 on Skylake)
which controls whether buffer 0 is relative to dynamic state base
address, or simply a normal
Kernel 4.16 has proper context isolation, which means we can change
the L3 configuration without worrying about that leaking to other
newly created contexts, breaking the assumptions of other userspace.
So, disable our workaround to reprogram it back to the default.
---
https://bugs.freedesktop.org/show_bug.cgi?id=105139
--- Comment #2 from Ilia Mirkin ---
OK, looks like the literal attach is legal, but then the framebuffer isn't
complete. From OpenGL 4.6:
"""
The framebuffer attachment point attachment is said to be framebuffer
https://bugs.freedesktop.org/show_bug.cgi?id=105139
--- Comment #1 from Ilia Mirkin ---
They're managing to attach a depth texture to a GL_COLOR_ATTACHMENT0? That
shouldn't be possible... but I don't see any logic blocking it in
framebuffer_texture_with_dims.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=105139
Bug ID: 105139
Summary: Assertion in Dying Light
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority:
On Thursday, February 15, 2018 9:18:51 PM PST Timothy Arceri wrote:
> ---
> src/compiler/glsl/glsl_to_nir.cpp | 5 +
> src/compiler/shader_info.h| 2 ++
> 2 files changed, 7 insertions(+)
>
> diff --git a/src/compiler/glsl/glsl_to_nir.cpp
> b/src/compiler/glsl/glsl_to_nir.cpp
>
Quoting Alexander von Gluck IV (2018-02-16 12:27:03)
> + link_with : [libglapi_static, libglapi],
> + dependencies : cpp.find_library('be'),
I think that we end up calling cpp.find_library('be') it might be worth just
adding this to the top meson.build file as dep_be, but I'm okay doing that as
Quoting Emil Velikov (2018-02-16 09:19:53)
> From: Emil Velikov
>
> Currently there are two type of users of NIR (and hence idep_nir):
> - gallium/aux - via tgsi_to_nir.c
> - drivers - freedreno, radeonsi, vc4, vc5
>
> Of the above, the aux. module and freedreno
Quoting Emil Velikov (2018-02-16 14:07:26)
> On 16 February 2018 at 19:08, Alexander von Gluck IV
> wrote:
> > February 16, 2018 11:49 AM, "Emil Velikov" wrote:
> >> Hi Alexander,
> >>
> >> Did you drop the ball on the autotools patches? I could
Quoting Emil Velikov (2018-02-16 14:21:52)
> On 16 February 2018 at 22:12, Dylan Baker wrote:
> > Quoting Emil Velikov (2018-02-16 13:55:06)
> >> On 16 February 2018 at 19:28, Dylan Baker wrote:
> >> > Quoting Alexander von Gluck IV (2018-02-16 11:08:33)
On 16 February 2018 at 22:12, Dylan Baker wrote:
> Quoting Emil Velikov (2018-02-16 13:55:06)
>> On 16 February 2018 at 19:28, Dylan Baker wrote:
>> > Quoting Alexander von Gluck IV (2018-02-16 11:08:33)
>> >> February 16, 2018 11:49 AM, "Emil Velikov"
Quoting Emil Velikov (2018-02-16 13:55:06)
> On 16 February 2018 at 19:28, Dylan Baker wrote:
> > Quoting Alexander von Gluck IV (2018-02-16 11:08:33)
> >> February 16, 2018 11:49 AM, "Emil Velikov"
> >> wrote:
> >> > Hi Alexander,
> >> >
> >> >
On 16 February 2018 at 19:22, Dylan Baker wrote:
> Quoting Emil Velikov (2018-02-16 10:49:05)
>> On 16 February 2018 at 17:28, Dylan Baker wrote:
>> > Quoting Emil Velikov (2018-02-16 09:23:01)
>> >> On 16 February 2018 at 17:15, Dylan Baker
On 16 February 2018 at 19:08, Alexander von Gluck IV
wrote:
> February 16, 2018 11:49 AM, "Emil Velikov" wrote:
>> Hi Alexander,
>>
>> Did you drop the ball on the autotools patches? I could re-spin them
>> but have no way to test.
>
> I've been
On 16 February 2018 at 19:28, Dylan Baker wrote:
> Quoting Alexander von Gluck IV (2018-02-16 11:08:33)
>> February 16, 2018 11:49 AM, "Emil Velikov" wrote:
>> > Hi Alexander,
>> >
>> > Did you drop the ball on the autotools patches? I could re-spin
Reviewed-by: Charmaine Lee
From: Brian Paul
Sent: Friday, February 16, 2018 12:59:28 PM
To: mesa-dev@lists.freedesktop.org
Cc: Charmaine Lee; Neha Bhende
Subject: [PATCH] svga: replaced 'unsigned' with proper
https://bugs.freedesktop.org/show_bug.cgi?id=105068
Bas Nieuwenhuizen changed:
What|Removed |Added
Severity|critical|normal
"This field controls the granularity of the replay mechanism when
coming back into a previously preempted context."
The kernel disables this bit but whitelists the register, and it's a
context register. So enable it and take advantage of finer granularity
when preemption is available.
---
src/gallium/drivers/svga/svga_tgsi_vgpu10.c | 33 ++---
1 file changed, 21 insertions(+), 12 deletions(-)
diff --git a/src/gallium/drivers/svga/svga_tgsi_vgpu10.c
b/src/gallium/drivers/svga/svga_tgsi_vgpu10.c
index 4d0834b..6b8337c 100644
---
---
include/meson.build| 8 +
meson.build| 16 +++---
src/egl/meson.build| 36 +++---
src/gallium/meson.build| 9 ++
Quoting Emil Velikov (2018-02-16 10:46:59)
> On 16 February 2018 at 17:58, Dylan Baker wrote:
> > Emil,
> >
> > If meson is going to work for their needs it seems silly to merge autotools
> > support, when the plan is to drop autotools from mesa in the coming year.
> >
>
Quoting Alexander von Gluck IV (2018-02-16 11:08:33)
> February 16, 2018 11:49 AM, "Emil Velikov" wrote:
> > Hi Alexander,
> >
> > Did you drop the ball on the autotools patches? I could re-spin them
> > but have no way to test.
>
> I've been focused on meson since
Quoting Emil Velikov (2018-02-16 10:49:05)
> On 16 February 2018 at 17:28, Dylan Baker wrote:
> > Quoting Emil Velikov (2018-02-16 09:23:01)
> >> On 16 February 2018 at 17:15, Dylan Baker wrote:
> >> > This fixes a race condition in building targets that
On Wed, Feb 14, 2018 at 03:53:19PM -0800, Nanley Chery wrote:
> On Wed, Feb 14, 2018 at 12:16:33PM -0800, Jason Ekstrand wrote:
> > Previously, we would always apply the layout transition at the beginning
> > of the subpass and then do the clear whether fast or slow. This meant
> > that there
February 16, 2018 11:49 AM, "Emil Velikov" wrote:
> Hi Alexander,
>
> Did you drop the ball on the autotools patches? I could re-spin them
> but have no way to test.
I've been focused on meson since it's the future.
Feel free to re-spin them if you have the bandwidth.
https://bugs.freedesktop.org/show_bug.cgi?id=105029
--- Comment #2 from Emil Velikov ---
Is there something broken on my end - the fix seems to be missing from the
list. Also we'll need the fix in stable since the offending commit landed in
17.2.0-devel
commit
On 16 February 2018 at 17:28, Dylan Baker wrote:
> Quoting Emil Velikov (2018-02-16 09:23:01)
>> On 16 February 2018 at 17:15, Dylan Baker wrote:
>> > This fixes a race condition in building targets that link in freedreno.
>> >
>> > cc: Mark Janes
On 16 February 2018 at 17:58, Dylan Baker wrote:
> Emil,
>
> If meson is going to work for their needs it seems silly to merge autotools
> support, when the plan is to drop autotools from mesa in the coming year.
>
What's wrong with having it until then? Comparing the two
On 16/02/18 17:53, James Zhu wrote:
> Hi Mark,
>
> I couldn't reproduce the issue on my Polaris 11 to run mpv / ffmpeg about 1.5
> hours.
>
> one terminal run:
>
> ffmpeg -y -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
> -hwaccel_output_format vaapi -i video/Mr.Right.mp4 -an -c:v
https://bugs.freedesktop.org/show_bug.cgi?id=105132
--- Comment #3 from Emil Velikov ---
Grr scratch that - I missed the negation in from of invalidateAvailable :-\
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=105132
--- Comment #2 from Emil Velikov ---
Could swear I pushed something on the topic - commit
c9d449de640f62d83149e64015029b466c44b12c. Which seems to be EGL/x11 :-(
invalidateAvailable is available only for DRI2 1.3+
Acked-by: Mark Janes
Dylan Baker writes:
> This fixes a race condition in building targets that link in freedreno.
>
> cc: Mark Janes
> Fixes: 0bbecc5a8548883f76a7 ("meson: define driver dependencies")
> Signed-off-by:
On Thu, Feb 15, 2018 at 6:07 PM, Jason Ekstrand wrote:
> On Thu, Feb 15, 2018 at 5:44 PM, Anuj Phogat wrote:
>>
>> Signed-off-by: Anuj Phogat
>> ---
>> src/intel/vulkan/genX_pipeline.c | 7 +++
>> 1 file changed, 7
Emil,
If meson is going to work for their needs it seems silly to merge autotools
support, when the plan is to drop autotools from mesa in the coming year.
Dylan
Quoting Emil Velikov (2018-02-16 09:49:37)
> Hi Alexander,
>
> Did you drop the ball on the autotools patches? I could re-spin them
On Thu, Feb 15, 2018 at 6:14 PM, Jason Ekstrand wrote:
> I made a few fairly trivial comments but it all looks pretty good.
>
> Reviewed-by: Jason Ekstrand
Thanks for the quick review Jason.
>
> On Thu, Feb 15, 2018 at 5:44 PM, Anuj Phogat
Hi Alexander,
Did you drop the ball on the autotools patches? I could re-spin them
but have no way to test.
There's a couple of comments inline, but nothing major.
On 16 February 2018 at 00:32, Alexander von Gluck IV
wrote:
> --- a/meson.build
> +++ b/meson.build
>
On Fri, Feb 16, 2018 at 9:44 AM, Anuj Phogat wrote:
> On Thu, Feb 15, 2018 at 6:13 PM, Jason Ekstrand
> wrote:
> > On Thu, Feb 15, 2018 at 5:44 PM, Anuj Phogat
> wrote:
> >>
> >> Signed-off-by: Anuj Phogat
On Thu, Feb 15, 2018 at 6:12 PM, Jason Ekstrand wrote:
>
>
> On Thu, Feb 15, 2018 at 5:44 PM, Anuj Phogat wrote:
>>
>> The PIPE_CONTROL command description says:
>>
>> "Whenever a Binding Table Index (BTI) used by a Render Taget Message
>> points to a
On Thu, Feb 15, 2018 at 6:13 PM, Jason Ekstrand wrote:
> On Thu, Feb 15, 2018 at 5:44 PM, Anuj Phogat wrote:
>>
>> Signed-off-by: Anuj Phogat
>> ---
>> src/intel/vulkan/genX_state.c | 2 +-
>> 1 file changed, 1 insertion(+), 1
https://bugs.freedesktop.org/show_bug.cgi?id=105132
Scott D Phillips changed:
What|Removed |Added
CC|
---
src/intel/vulkan/anv_formats.c | 9 +++
src/intel/vulkan/anv_image.c | 53 ++
2 files changed, 42 insertions(+), 20 deletions(-)
diff --git a/src/intel/vulkan/anv_formats.c b/src/intel/vulkan/anv_formats.c
index 9c52ad5..3c17366 100644
---
Quoting Emil Velikov (2018-02-16 09:23:01)
> On 16 February 2018 at 17:15, Dylan Baker wrote:
> > This fixes a race condition in building targets that link in freedreno.
> >
> > cc: Mark Janes
> > Fixes: 0bbecc5a8548883f76a7 ("meson: define driver
From: Emil Velikov
Currently there are two type of users of NIR (and hence idep_nir):
- gallium/aux - via tgsi_to_nir.c
- drivers - freedreno, radeonsi, vc4, vc5
Of the above, the aux. module and freedreno were missing the idep_nir.
Adjust as needed and document.
On 16 February 2018 at 17:15, Dylan Baker wrote:
> This fixes a race condition in building targets that link in freedreno.
>
> cc: Mark Janes
> Fixes: 0bbecc5a8548883f76a7 ("meson: define driver dependencies")
> Signed-off-by: Dylan Baker
Quoting Alexander von Gluck IV (2018-02-15 16:58:35)
> February 15, 2018 6:36 PM, "Dylan Baker" wrote:
>
> > Quoting Alexander von Gluck IV (2018-02-15 16:04:37)
> >
> >> I'm actually not 100% sure here. I have missing symbols at link without
> >> both
> >> included. More
Reviewed-by: Jason Ekstrand
We'll get it right one of these days!
On Fri, Feb 16, 2018 at 2:52 AM, Daniel Stone wrote:
> The previous commit reworked the checks intel_from_planar() to check the
> right individual cases for regular/planar/aux
This fixes a race condition in building targets that link in freedreno.
cc: Mark Janes
Fixes: 0bbecc5a8548883f76a7 ("meson: define driver dependencies")
Signed-off-by: Dylan Baker
---
src/gallium/drivers/freedreno/meson.build | 1 +
1 file
https://bugs.freedesktop.org/show_bug.cgi?id=105029
George Kyriazis changed:
What|Removed |Added
Resolution|--- |FIXED
Enable UVD encode for HEVC main profile
Signed-off-by: James Zhu
Reviewed-by: Boyuan Zhang
---
src/gallium/drivers/radeonsi/si_get.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/gallium/drivers/radeonsi/si_get.c
Implement required IBs for UVD HEVC encode.
Signed-off-by: James Zhu
Reviewed-by: Boyuan Zhang
---
src/gallium/drivers/radeon/Makefile.sources |1 +
src/gallium/drivers/radeon/meson.build |1 +
Add UVD hevc encode pipe video codec creation entry
Signed-off-by: James Zhu
Reviewed-by: Boyuan Zhang
---
src/gallium/drivers/radeonsi/si_uvd.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git
Implement UVD hevc encode functions
Signed-off-by: James Zhu
Reviewed-by: Boyuan Zhang
---
src/gallium/drivers/radeon/Makefile.sources | 1 +
src/gallium/drivers/radeon/meson.build | 1 +
src/gallium/drivers/radeon/radeon_uvd_enc.c | 381
The whole series are the updated version. Changes are made mainly
based on the comments from prevous code review from Alex, Leo,
Boyuan, Bas, Marek, Christian and Mark
James Zhu (7):
amd/common:add uvd hevc enc support check in hw query
winsys/amdgpu:add uvd hevc enc support in amdgpu cs
Support UVD HEVC encode in amdgpu cs
Signed-off-by: James Zhu
Reviewed-by: Boyuan Zhang
---
src/gallium/winsys/amdgpu/drm/amdgpu_cs.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/gallium/winsys/amdgpu/drm/amdgpu_cs.c
Add hevc encode hardware interface for UVD
Signed-off-by: James Zhu
Reviewed-by: Boyuan Zhang
---
src/gallium/drivers/radeon/Makefile.sources | 1 +
src/gallium/drivers/radeon/meson.build | 1 +
src/gallium/drivers/radeon/radeon_uvd_enc.h | 469
Based on amdgpu hardware query information to check if UVD hevc enc support
Signed-off-by: James Zhu
Reviewed-by: Marek Olšák
---
src/amd/common/ac_gpu_info.c | 12 +++-
src/amd/common/ac_gpu_info.h | 1 +
2 files changed, 12 insertions(+), 1
https://bugs.freedesktop.org/show_bug.cgi?id=105132
Bug ID: 105132
Summary: glxSwapBuffers has no effect
Product: Mesa
Version: unspecified
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=93551
--- Comment #49 from Thomas J. Moore ---
(In reply to Alex from comment #48)
> Yes, the shim seems to no longer work -- I assume newer Mesa versions are no
> longer declaring compatibility with whatever version Divinity was
From: Mikko Perttunen
GP10B requires the use of GP100_COMPUTE_CLASS instead of
GP104_COMPUTE_CLASS as is used for other non-GP100 chips.
Signed-off-by: Mikko Perttunen
---
src/gallium/drivers/nouveau/nvc0/nve4_compute.c | 3 ++-
1 file changed, 2
From: Gustavo Padovan
Following the support for fences on the virtio driver add support
for native fence on virgl. This was somewhat based on the freedeno one.
Signed-off-by: Gustavo Padovan
---
The kernel side patches can be found
On Fri, Feb 16, 2018 at 11:33 PM, Robert Foss wrote:
> Hey Tomasz,
>
>
> On 02/16/2018 05:10 AM, Tomasz Figa wrote:
>>
>> On Fri, Feb 9, 2018 at 11:06 PM, Rob Herring wrote:
>>>
>>> On Fri, Feb 9, 2018 at 3:58 AM, Tomasz Figa
Hey Tomasz,
On 02/16/2018 05:10 AM, Tomasz Figa wrote:
On Fri, Feb 9, 2018 at 11:06 PM, Rob Herring wrote:
On Fri, Feb 9, 2018 at 3:58 AM, Tomasz Figa wrote:
On Fri, Feb 2, 2018 at 11:51 PM, Tomasz Figa wrote:
On Fri, Feb 2, 2018 at
https://bugs.freedesktop.org/show_bug.cgi?id=105103
Daniel Stone changed:
What|Removed |Added
Status|NEW |RESOLVED
On 16 February 2018 at 13:56, Emil Velikov wrote:
> On 15 February 2018 at 13:13, Emil Velikov wrote:
>> On 15 February 2018 at 09:23, Daniel Stone wrote:
>>> A recent patchset to Wayland[0] migrated Mesa's
On 15 February 2018 at 13:13, Emil Velikov wrote:
> On 15 February 2018 at 09:23, Daniel Stone wrote:
>> A recent patchset to Wayland[0] migrated Mesa's libwayland-egl backend
>> into Wayland itself, so implementations could provide backends. Mesa
Entire set Reviewed-by: Bruce Cherniak
> On Feb 13, 2018, at 4:42 PM, George Kyriazis
> wrote:
>
> Batch patchset of SWR rasterizer-related changes
>
> George Kyriazis (31):
> swr/rast: Add missing parameter to a few gather functions
>
Hi Ilia,
On 10 February 2018 at 01:49, Ilia Mirkin wrote:
> The GBM surface format has to match the DRM mode. Both are used in a
> couple of places, so unify it so that it's only set in one place. Note
> that the GBM and DRM formats are identical.
Pushed this one to master
Hi Jason, I have just noticed that this series also conflicts with the
new version of the multiview clearing series I have just sent, I guess
we should wait until this lands first?
Iago
On Wed, 2018-02-14 at 12:16 -0800, Jason Ekstrand wrote:
> This is another version of my patch series to
We can call this for both subpass load clears and VkCmdClearAttachments.
In the former case, when multiview is active, we need to honor the mask
of pending clear views so we don't clear layers that have already been
cleared by a previous subpass, just like we do for subpass load color
clears.
---
blorp_gen8_hiz_clear_attachments only clears the first layer.
v2:
- do this in all cases, not just when multiview is involved.
- rebased on top of fast-clear rework.
---
src/intel/vulkan/anv_blorp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/intel/vulkan/anv_blorp.c
When multiview is active a subpass clear may only clear a subset of the
attachment layers. Other subpasses in the same render pass may also
clear too and we want to honor those clears as well, however, we need to
ensure that we only clear a layer once, on the first subpass that uses
a particular
Hi,
On 15 February 2018 at 22:44, Jason Ekstrand wrote:
> On Thu, Feb 15, 2018 at 7:57 AM, Daniel Stone wrote:
>> + draw->ext->image->queryDmaBufModifiers(draw->dri_screen, format,
>> +
Am Freitag, den 16.02.2018, 14:44 +1000 schrieb Dave Airlie:
> From: Dave Airlie
>
> A bunch of CTS tests led me to write
> tests/shaders/ssa/fs-while-loop-rotate-value.shader_test
> which r600/sb always fell over on.
>
> GCM seems to move some of the copys into other basic
https://bugs.freedesktop.org/show_bug.cgi?id=105098
Bas Nieuwenhuizen changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
On 15 February 2018 at 21:38, Jason Ekstrand wrote:
> On Thu, Feb 15, 2018 at 7:57 AM, Daniel Stone wrote:
>> @@ -138,7 +140,7 @@ wsi_x11_connection_create(const VkAllocationCallbacks
>> *alloc,
>>return NULL;
>>
>> dri3_cookie =
Hi,
On 15 February 2018 at 19:46, Jason Ekstrand wrote:
> On Thu, Feb 15, 2018 at 7:57 AM, Daniel Stone wrote:
>> + image_modifier_count = 0;
>> + for (uint32_t l = 0; l < num_modifier_lists; l++) {
>> + /* Walk the modifier lists
The previous commit reworked the checks intel_from_planar() to check the
right individual cases for regular/planar/aux buffers, and do size
checks in all cases.
Unfortunately, the aux size check was broken, and required the aux
surface to be allocated with the correct aux stride, but full image
On 16 February 2018 at 09:31, Juan A. Suarez Romero wrote:
> On Thu, 2018-02-15 at 12:56 +, Emil Velikov wrote:
>> Mesa 17.3.4 is now available.
>>
>> In this release we have:
>>
>> Dozens of fixes in the i965, ANV and RADV drivers. Additionally
>> the r600, virgl,
Vega stats should be:
Totals from affected shaders:
SGPRS: 106088 -> 106232 (0.14 %)
VGPRS: 74652 -> 74700 (0.06 %)
Spilled SGPRs: 692 -> 658 (-4.91 %)
Code Size: 2967708 -> 2953028 (-0.49 %) bytes
Max Waves: 18178 -> 18162 (-0.09 %)
My local override family was wrong because I have plugged my
Useful for pipeline-db.
Signed-off-by: Samuel Pitoiset
---
src/amd/vulkan/radv_device.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
index 09bb382eeb..98cfd9b58a
https://bugs.freedesktop.org/show_bug.cgi?id=104662
mirh changed:
What|Removed |Added
CC||m...@protonmail.ch
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=104662
mirh changed:
What|Removed |Added
Priority|medium |low
v2: update conditional
Signed-off-by: Samuel Pitoiset
---
src/amd/common/ac_nir_to_llvm.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/src/amd/common/ac_nir_to_llvm.c b/src/amd/common/ac_nir_to_llvm.c
index dc471de977..12f097e2b2
On Thu, 2018-02-15 at 12:56 +, Emil Velikov wrote:
> Mesa 17.3.4 is now available.
>
> In this release we have:
>
> Dozens of fixes in the i965, ANV and RADV drivers. Additionally
> the r600, virgl, etnaviv and renderonly drivers have also seen some love.
>
> The experimental Vulkan
It makes no sense to compact before, and the description of
nir_compact_varyings() confirms that.
Polaris10:
Totals from affected shaders:
SGPRS: 108528 -> 108128 (-0.37 %)
VGPRS: 74548 -> 74500 (-0.06 %)
Spilled SGPRs: 844 -> 814 (-3.55 %)
Code Size: 3007328 -> 2992932 (-0.48 %) bytes
Max Waves:
90 matches
Mail list logo