From: Marek Olšák
---
src/compiler/nir/nir.h| 8 +
src/compiler/nir/nir_opt_intrinsics.c | 40 +--
src/gallium/drivers/radeonsi/si_get.c | 1 +
src/mesa/state_tracker/st_glsl_to_nir.cpp | 1 +
4 files changed, 48 insertions(+), 2
On 13/2/19 8:57 am, Andres Gomez wrote:
From page 76 (page 80 of the PDF) of the GLSL 4.60 v.5 spec:
" No aliasing in output buffers is allowed: It is a compile-time or
link-time error to specify variables with overlapping transform
feedback offsets."
Currently, this is expected
Acked-by: Timothy Arceri
On 10/4/19 9:39 am, Marek Olšák wrote:
From: Marek Olšák
for Viewperf 13
---
src/compiler/glsl/glsl_parser.yy | 9 +
1 file changed, 9 insertions(+)
diff --git a/src/compiler/glsl/glsl_parser.yy b/src/compiler/glsl/glsl_parser.yy
index
On Mon, Apr 8, 2019 at 10:32 PM Dieter Nützel wrote:
> Am 09.04.2019 02:42, schrieb Marek Olšák:
> > I'm pretty sure I merged this series in February.
> >
> > Marek
>
> Yes, of course you did (with my tb), but I meant... (see below)
>
> > On Mon, Apr 8, 2019 at 6:10 PM Dieter Nützel
> > wrote:
From: Marek Olšák
for Viewperf 13
---
src/compiler/glsl/glsl_parser.yy | 9 +
1 file changed, 9 insertions(+)
diff --git a/src/compiler/glsl/glsl_parser.yy b/src/compiler/glsl/glsl_parser.yy
index 8d6c47fb6a3..b91c24ebe97 100644
--- a/src/compiler/glsl/glsl_parser.yy
+++
Fine by me, but please improve the drm.h description, see below.
With that changed, this is:
Reviewed-by: Axel Davy
Axel
On 08/04/2019 09:10, Andre Heider wrote:
For HW cursors, "cursor.pos" doesn't hold the current position of the
pointer, just the position of the last call to
On Tue, Apr 9, 2019 at 1:29 PM Jan Vesely wrote:
>
> On Sat, Apr 6, 2019 at 10:11 PM Dieter Nützel wrote:
> >
> > Tested-by: Dieter Nützel
> > Acked-by: Dieter Nützel
>
> Thanks Dieter,
>
> Timur, Vinson, are you OK with this temporary solution?
>
> Jan
>
Tested-by: Vinson Lee
> >
> > Thank
a-b now.
On Mon, Apr 8, 2019 at 9:31 AM Samuel Pitoiset
wrote:
>
>
> On 3/21/19 11:09 AM, Bas Nieuwenhuizen wrote:
> > Honestly the zero tests is worrying me. This is a pretty big extension
> > and I have questions like:
> >
> > to 16-bit loads + 16-bit ALU actually work together or have we been
r-b for both.
On Mon, Apr 8, 2019 at 9:22 AM Samuel Pitoiset
wrote:
>
> From: Rhys Perry
>
> Signed-off-by: Rhys Perry
> ---
> src/amd/common/ac_llvm_build.c | 22 +-
> 1 file changed, 17 insertions(+), 5 deletions(-)
>
> diff --git a/src/amd/common/ac_llvm_build.c
On Wed, Apr 3, 2019 at 2:02 AM Jan Vesely wrote:
>
> Skip over non-existent files.
> Signed-off-by: Jan Vesely
> ---
> This should help detect instances of messed up/missing symbols in the driver.
> windows build seems OK:
> https://ci.appveyor.com/project/jvesely/mesa/builds/23550498#L1292
>
On Sat, Apr 6, 2019 at 10:11 PM Dieter Nützel wrote:
>
> Tested-by: Dieter Nützel
> Acked-by: Dieter Nützel
Thanks Dieter,
Timur, Vinson, are you OK with this temporary solution?
Jan
>
> Thank you Jan!
>
> BTW More about 'meson' with radeonsi and Clover in some hours.
>
> Dieter
>
> Am
On 4/9/19 12:23 AM, Sahu, Satyajit wrote:
> On 4/9/2019 12:34 AM, Liu, Leo wrote:
>> On 4/8/19 1:17 AM, Sahu, Satyajit wrote:
>>> From: suresh guttula
>>>
>>> This patch will add support for frame_cropping when the input size is not
>>> matched with aligned size. Currently vaapi driver ignores
https://bugs.freedesktop.org/show_bug.cgi?id=110345
--- Comment #5 from Thomas Rohloff ---
(In reply to Samuel Pitoiset from comment #4)
> I got a hang one time when starting a new race, I'm not sure how to
> reproduce it again. Like you said, it's random and that will be a huge pain
> to figure
Topi, Are you also planning to send out a similar patch for Iris ?
Thanks
Anuj
On Mon, Apr 8, 2019 at 4:20 PM Anuj Phogat wrote:
>
> On Wed, Mar 27, 2019 at 9:47 AM Topi Pohjolainen
> wrote:
> >
> > Similarly to 1cc17fb731466c68586915acbb916586457b19bc
> >
> > Fixes gpu hangs with
https://bugs.freedesktop.org/show_bug.cgi?id=110345
--- Comment #4 from Samuel Pitoiset ---
I got a hang one time when starting a new race, I'm not sure how to reproduce
it again. Like you said, it's random and that will be a huge pain to figure
out.
--
You are receiving this mail because:
You
On Mon, Apr 8, 2019 at 10:46 AM Michel Dänzer wrote:
>
> On 2019-04-02 4:00 p.m., Michel Dänzer wrote:
> > On 2019-04-02 2:57 p.m., Marek Olšák wrote:
> >> On Tue, Apr 2, 2019 at 4:57 AM Michel Dänzer wrote:
> >>> On 2019-04-02 12:39 a.m., Marek Olšák wrote:
> On Mon, Apr 1, 2019 at 1:28 PM
Quoting Eero Tamminen (2019-04-09 05:33:50)
> Hi,
>
> On 9.4.2019 14.16, Ernst Sjöstrand wrote:
> > For people building newer Mesa pip3 install --user meson is quite a
> > lot better and more accessible.
>
> Nice thing with backports is that they get upgraded when one upgrades
> rest of the
Quoting Eero Tamminen (2019-04-09 04:14:21)
> Hi,
>
> On 9.4.2019 0.22, Dylan Baker wrote:
> > It would be nice if people wouldn't try to build bleeding edge mesa on a 12
> > year
> > old distro :D. Unfortunately as Eero ppoints out they do. I'd like to bump
> > the
> > meson version to 0.47 in
Hi Andres,
This doesn't apply cleanly to the 19.0 branch, and I'm not even sure where to
start resolving the conflicts. If you still want this in 19.0 can you backport
this and either create an MR against the staging/19.0 branch and mention me, or
send a patch to the stable list and CC me? (I
https://bugs.freedesktop.org/show_bug.cgi?id=110350
--- Comment #7 from Samuel Pitoiset ---
Can you eventually bisect?
Unfortunately, I don't have a Vega20.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110350
--- Comment #6 from Thomas Crider ---
Issue does -not- occur on mesa-git + llvm 8, so looks like it's an llvm issue
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
On 4/9/19 4:22 PM, Lionel Landwerlin wrote:
There is a small nit below which you don't have to apply.
With the correct bug reference :
Reviewed-by: Lionel Landwerlin
On 09/04/2019 15:18, Samuel Pitoiset wrote:
This is common to all Vulkan drivers and all WSI.
v3: - move the invalid check
There is a small nit below which you don't have to apply.
With the correct bug reference :
Reviewed-by: Lionel Landwerlin
On 09/04/2019 15:18, Samuel Pitoiset wrote:
This is common to all Vulkan drivers and all WSI.
v3: - move the invalid check in wsi_device_init()
- use
This is common to all Vulkan drivers and all WSI.
v3: - move the invalid check in wsi_device_init()
- use VK_PRESENT_MODE_MAX_ENUM_KHR as default value
v2: - store the override in wsi_device_init()
- do not abort when an invalid value is detected
- check supported present modes
On 4/9/19 3:52 PM, Lionel Landwerlin wrote:
On 09/04/2019 14:31, Samuel Pitoiset wrote:
This is common to all Vulkan drivers and all WSI.
v2: - store the override in wsi_device_init()
- do not abort when an invalid value is detected
- check supported present modes
Bugzilla:
On 09/04/2019 14:31, Samuel Pitoiset wrote:
This is common to all Vulkan drivers and all WSI.
v2: - store the override in wsi_device_init()
- do not abort when an invalid value is detected
- check supported present modes
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107391
https://bugs.freedesktop.org/show_bug.cgi?id=109565
Samuel Pitoiset changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
This is common to all Vulkan drivers and all WSI.
v2: - store the override in wsi_device_init()
- do not abort when an invalid value is detected
- check supported present modes
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107391
Signed-off-by: Samuel Pitoiset
---
https://bugs.freedesktop.org/show_bug.cgi?id=109565
--- Comment #12 from Jakub Okoński ---
I don't think so, like I said I wasn't using dynamic offsets at all, maybe
validation layers added something but I'm not sure anymore.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109565
--- Comment #11 from Samuel Pitoiset ---
I assume it was a bug on your side?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev
On 09/04/2019 13:29, Samuel Pitoiset wrote:
On 4/9/19 1:10 PM, Lionel Landwerlin wrote:
On 09/04/2019 08:08, Samuel Pitoiset wrote:
This is common to all Vulkan drivers and all WSI.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107391
Signed-off-by: Samuel Pitoiset
---
https://bugs.freedesktop.org/show_bug.cgi?id=109565
--- Comment #10 from Jakub Okoński ---
Nope, I made some unrelated changes and I'm not hitting this problem anymore.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110323
--- Comment #1 from john.frank...@outlook.com ---
Note that the same error occurs with meson, both autotools and meson builds
using gcc-8.2.0
FAILED:
src/gallium/drivers/swr/3eb908b@@mesaswr@sta/rasterizer_jitter_builder_mem.cpp.o
g++
On 4/9/19 1:10 PM, Lionel Landwerlin wrote:
On 09/04/2019 08:08, Samuel Pitoiset wrote:
This is common to all Vulkan drivers and all WSI.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107391
Signed-off-by: Samuel Pitoiset
---
src/vulkan/wsi/wsi_common.c | 19
Hi,
On 9.4.2019 14.16, Ernst Sjöstrand wrote:
For people building newer Mesa pip3 install --user meson is quite a
lot better and more accessible.
Nice thing with backports is that they get upgraded when one upgrades
rest of the distro.
It's probably less of an issue with Python than some
https://bugs.freedesktop.org/show_bug.cgi?id=110350
--- Comment #5 from Samuel Pitoiset ---
Could be something specific to Vega20 as it renders correctly for me on
Vega10+mesa-git+llvm-git.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the
On Tuesday, 2019-04-09 13:16:16 +0200, Ernst Sjöstrand wrote:
> For people building newer Mesa pip3 install --user meson is quite a
> lot better and more accessible.
Agreed: if users want a recent version of meson, they might as well
install the current one from pip instead of some slightly less
https://bugs.freedesktop.org/show_bug.cgi?id=110350
--- Comment #4 from Samuel Pitoiset ---
Does it render correctly with Mesa-git + LLVM 8.0.0 ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
Hi,
On Fri, Mar 29, 2019 at 05:48:31PM +0100, Guido Günther wrote:
> Without that kmscube with GALLIUM_TRACE would segfault like:
>
> #0 0x in ()
> #1 0x8f311760 in dri2_create_fence_fd (_ctx=0xe266b8b0, fd=10)
> at
For people building newer Mesa pip3 install --user meson is quite a
lot better and more accessible.
Not a solutions for distributions that want to backport newer Mesa etc though.
Those build dependencies look more like runtime dependencies btw,
Meson is just pure python right?
Regards
//Ernst
On 09/04/2019 08:08, Samuel Pitoiset wrote:
This is common to all Vulkan drivers and all WSI.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107391
Signed-off-by: Samuel Pitoiset
---
src/vulkan/wsi/wsi_common.c | 19 +++
src/vulkan/wsi/wsi_common_display.c |
I'll add locally to the commit log:
Fixes the following test:
KHR-GL44.enhanced_layouts.xfb_output_overlapping
On Tue, 2019-02-12 at 23:57 +0200, Andres Gomez wrote:
> From page 76 (page 80 of the PDF) of the GLSL 4.60 v.5 spec:
>
> " No aliasing in output buffers is allowed: It is a
Hi,
On 9.4.2019 0.22, Dylan Baker wrote:
It would be nice if people wouldn't try to build bleeding edge mesa on a 12 year
old distro :D. Unfortunately as Eero ppoints out they do. I'd like to bump the
meson version to 0.47 in the future for some of the other features it adds
(automatically
https://bugs.freedesktop.org/show_bug.cgi?id=110345
--- Comment #3 from Thomas Rohloff ---
(In reply to Thomas Rohloff from comment #2)
> instead of continuing after finish just let the reply run
I meaned "replay", sorry.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110345
--- Comment #2 from Thomas Rohloff ---
(In reply to Samuel Pitoiset from comment #1)
> What preset and what llvm are you using?
With preset you mean the in-game graphics preset, right? If so I'm using Ultra
(everything maxed out).
I started
https://bugs.freedesktop.org/show_bug.cgi?id=110345
--- Comment #1 from Samuel Pitoiset ---
What preset and what llvm are you using?
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
On 2019-04-09 at 10:56, Michel Dänzer wrote:
> On 2019-04-09 10:03 a.m., Eric Engestrom wrote:
> > On Tuesday, 2019-04-09 09:08:36 +0200, Samuel Pitoiset wrote:
> >>
> >> + if (!strcmp(mode, "fifo")) {
> >> + swapchain->present_mode = VK_PRESENT_MODE_FIFO_KHR;
> >> + } else if
On 2019-04-09 10:03 a.m., Eric Engestrom wrote:
> On Tuesday, 2019-04-09 09:08:36 +0200, Samuel Pitoiset wrote:
>>
>> + if (!strcmp(mode, "fifo")) {
>> + swapchain->present_mode = VK_PRESENT_MODE_FIFO_KHR;
>> + } else if (!strcmp(mode, "mailbox")) {
>> +
https://bugs.freedesktop.org/show_bug.cgi?id=109599
--- Comment #15 from tempel.jul...@gmail.com ---
It seems this is not limited to a single game, but a general issue. I could
reproduce the behavior in Hitman 2, there are again some shadows missing with
radv.
radv:
https://bugs.freedesktop.org/show_bug.cgi?id=110356
Mike Lothian changed:
What|Removed |Added
CC||m...@fireburn.co.uk
--- Comment #3 from
Nice move to put the logic in its own function!
Reviewed-by: Erik Faye-Lund
On Mon, 2019-04-08 at 09:39 -0700, Lepton Wu wrote:
> virgl render complains about "Illegal resource" when running
> dEQP-EGL.functional.color_clears.single_context.gles2.rgb888_window,
> the reason is that a zero bind
https://bugs.freedesktop.org/show_bug.cgi?id=110356
--- Comment #2 from Eric Engestrom ---
Should be fixed by https://gitlab.freedesktop.org/mesa/mesa/merge_requests/608
Could you give it a try?
--
You are receiving this mail because:
You are the QA Contact for the
On Tuesday, 2019-04-09 09:08:36 +0200, Samuel Pitoiset wrote:
> This is common to all Vulkan drivers and all WSI.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107391
> Signed-off-by: Samuel Pitoiset
> ---
> src/vulkan/wsi/wsi_common.c | 19 +++
>
This is common to all Vulkan drivers and all WSI.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107391
Signed-off-by: Samuel Pitoiset
---
src/vulkan/wsi/wsi_common.c | 19 +++
src/vulkan/wsi/wsi_common_display.c | 2 ++
src/vulkan/wsi/wsi_common_private.h | 2
https://bugs.freedesktop.org/show_bug.cgi?id=110356
Eric Engestrom changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |fdo-b...@engestrom.ch
On 4/9/19 6:45 AM, Jason Ekstrand wrote:
Why not just do this in a way that common to the two drivers? Forcing
FIFO and MAILBOX both seem useful. For that matter, why not just
MESA_VK_WSI_PRESENT_MODE=FIFO/mailbox/immediate?
Yes, looks fine.
On April 8, 2019 13:39:20 Samuel Pitoiset
On Mon, 2019-04-08 at 12:00 -0700, Francisco Jerez wrote:
> "Juan A. Suarez Romero" writes:
>
> > From: Iago Toral Quiroga
> >
> > v2: f32to16/f16to32 can use a :W destination (Curro)
> > ---
> > src/intel/compiler/brw_fs.cpp | 71
> > +++
> > 1 file changed,
57 matches
Mail list logo
