https://bugs.freedesktop.org/show_bug.cgi?id=110724
Tapani Pälli changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 5/23/19 8:22 PM, Sumit Semwal wrote:
Hi Eric,
On Thu, 23 May 2019 at 20:25, Eric Engestrom wrote:
On Thursday, 2019-05-23 08:34:40 +0300, Tapani Pälli wrote:
Hi;
On 5/22/19 9:20 PM, Alistair Strachan wrote:
On Tue, May 21, 2019 at 10:10 PM Tapani Pälli wrote:
On 5/21/19 4:53 PM,
How does max(NaN, 0) work? IIRC there's some provision that this
becomes 0, while abs(NaN) = NaN.
On Thu, May 23, 2019 at 10:47 PM Alyssa Rosenzweig wrote:
>
> I noticed this pattern in glmark's jellyfish scene.
>
> Assuming this is correct (it should be...?), could someone do a
> shader-db run?
I noticed this pattern in glmark's jellyfish scene.
Assuming this is correct (it should be...?), could someone do a
shader-db run? Thank you!
Signed-off-by: Alyssa Rosenzweig
Cc: Ian Romanick
---
src/compiler/nir/nir_opt_algebraic.py | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Roland Scheidegger
The x86asmprinter component is gone, and things seem to work by just
removing it.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110707
---
scons/llvm.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/scons/llvm.py b/scons/llvm.py
index
From: Roland Scheidegger
The default null_output really needs to be static, otherwise the values
we'll eventually get later are doubly random (they are not initialized,
and even if they were it's a pointer to a local stack variable).
VMware bug 2349556.
---
Hi Eric,
On Thu, 23 May 2019 at 20:25, Eric Engestrom wrote:
>
> On Thursday, 2019-05-23 08:34:40 +0300, Tapani Pälli wrote:
> > Hi;
> >
> > On 5/22/19 9:20 PM, Alistair Strachan wrote:
> > > On Tue, May 21, 2019 at 10:10 PM Tapani Pälli
> > > wrote:
> > > >
> > > >
> > > > On 5/21/19 4:53 PM,
Reviewed-by: Charmaine Lee
From: Brian Paul
Sent: Monday, May 20, 2019 6:36:33 AM
To: mesa-dev@lists.freedesktop.org
Cc: Neha Bhende; Charmaine Lee
Subject: [PATCH] svga: clamp max_const_buffers to SVGA_MAX_CONST_BUFS
In case the device reports 15 (or
Reviewed-by: Kristian H. Kristensen
On Thu, May 23, 2019 at 9:52 AM Brian Paul wrote:
>
> Ping.
>
> -Brian
>
> On 05/20/2019 07:36 AM, Brian Paul wrote:
> > Silence two unused var warnings. And init elem_size, elem_align to
> > zero to silence "maybe uninitialized" warnings.
> > ---
> >
Ping.
-Brian
On 05/20/2019 07:36 AM, Brian Paul wrote:
Silence two unused var warnings. And init elem_size, elem_align to
zero to silence "maybe uninitialized" warnings.
---
src/compiler/nir/nir_lower_int_to_float.c | 2 +-
src/compiler/nir/nir_opt_copy_prop_vars.c | 4 +---
https://bugs.freedesktop.org/show_bug.cgi?id=110357
--- Comment #3 from Eric Engestrom ---
(In reply to Juan A. Suarez from comment #2)
> This bug is a blocker for 19.1.0.
Is reverting dacb11a585 enough to fix the issue?
If so, I'd suggest doing that, and a new attempt can land after however
https://bugs.freedesktop.org/show_bug.cgi?id=110357
Eric Engestrom changed:
What|Removed |Added
CC||fdo-b...@engestrom.ch
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=110357
Kenneth Graunke changed:
What|Removed |Added
CC||intel-3d-bugs@lists.freedes
https://bugs.freedesktop.org/show_bug.cgi?id=110357
Kenneth Graunke changed:
What|Removed |Added
Component|Drivers/DRI/i965|EGL
On Thursday, 2019-05-23 08:34:40 +0300, Tapani Pälli wrote:
> Hi;
>
> On 5/22/19 9:20 PM, Alistair Strachan wrote:
> > On Tue, May 21, 2019 at 10:10 PM Tapani Pälli
> > wrote:
> > >
> > >
> > > On 5/21/19 4:53 PM, Sumit Semwal wrote:
> > > > Hello everyone,
> > > >
> > > > First up, my
The old code was not wrong because the transitions performed
after the resolves should re-emit the framebuffer if needed.
This change is mostly a no-op but it improves consistency
regarding other meta operations that need to save/restore subpasses.
Signed-off-by: Samuel Pitoiset
---
On 05/23/2019 02:48 AM, Erik Faye-Lund wrote:
On Wed, 2019-05-22 at 18:06 +0200, Akim Demaille wrote:
Hi Erik,
Le 22 mai 2019 à 08:54, Erik Faye-Lund <
erik.faye-l...@collabora.com> a écrit :
I ended up reverting the change [from-%error-verbose to %define
parse.error verbose] , and I can't
https://bugs.freedesktop.org/show_bug.cgi?id=110724
--- Comment #6 from Alberto Salvia Novella ---
Reported this info as:
https://github.com/RPCS3/rpcs3/issues/6007
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the
On Wed, 2019-05-22 at 18:06 +0200, Akim Demaille wrote:
> Hi Erik,
>
> > Le 22 mai 2019 à 08:54, Erik Faye-Lund <
> > erik.faye-l...@collabora.com> a écrit :
> >
> > I ended up reverting the change [from-%error-verbose to %define
> > parse.error verbose] , and I can't find an obcious way to
> >
On Wed, 2019-05-22 at 20:41 +0200, Akim Demaille wrote:
> > Le 22 mai 2019 à 18:06, Akim Demaille a écrit
> > :
> >
> > Hi Erik,
> >
> > > Le 22 mai 2019 à 08:54, Erik Faye-Lund <
> > > erik.faye-l...@collabora.com> a écrit :
> > > The Android SDK also ships a pre-3.x version of Bison, so
https://bugs.freedesktop.org/show_bug.cgi?id=110724
--- Comment #5 from Alberto Salvia Novella ---
So is this a bug in the emulator itself?
--
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=110724
--- Comment #4 from Tapani Pälli ---
And because glTexStorage2D fails it is likely that is why the following
glGetTexLevelParameteriv for that texture fail.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=110724
--- Comment #3 from Tapani Pälli ---
Playback of the trace throws following error:
Mesa: User error: GL_INVALID_VALUE in glTexStorage2D(width, height or depth <
1)
It looks like the emulator is making following invalid call:
Thanks for pointing this out, I will implement.
On 5/22/19 10:20 PM, Marek Olšák wrote:
The depth decompress pass needs to know the sample locations.
If shader loads read from compressed depth, the texture hardware will
always use the standard locations for decompression.
Marek
On Tue, May
24 matches
Mail list logo
