dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111241] Shadertoy shader causing hang
Date: Mon, 02 Sep 2019 23:47:12 +0000	[thread overview]
Message-ID: <bug-111241-502-E6PgZpRYJw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111241-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1963 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111241

Timothy Arceri <t_arceri@yahoo.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #13 from Timothy Arceri <t_arceri@yahoo.com.au> ---
(In reply to Dieter Nützel from comment #12)
> (In reply to Pierre-Eric Pelloux-Prayer from comment #11)
> > (In reply to Dieter Nützel from comment #8)
> > > BTW
> > > 
> > > Pierre-Eric can you look into this
> > > 
> > > Shadertoy shader corruption, too?
> > > https://www.shadertoy.com/view/Xt3cWS
> > >
> > 
> > The "Buffer A" shader doesn't write fragColor when uv.y is < 0.1 or > 0.9.
> > 
> > So the content is undefined and may be black on some platform or random.
> > 
> > radeonsi is correct here, but we might want to replace undef values with 0x0
> > to get a default value instead of random.
> 
> Cool to have you around for bug hunting...;-)
> 
> Any hints where I shoud change 'undef values with 0x0' for testing?
> 
> And sorry that I 'hijacked' this thread - should I open a new ticket?

I don't think you need to open a bug for it at all. As its not a bug in Mesa
its a shader bug.

Closing this bug report as it should be fixed by:

commit  47cc660d9c19572e5ef2dce7c8ae1766a2ac9885
glsl: replace 'x + (-x)' with constant 0
   This fixes a hang in shadertoy for radeonsi where a buffer was initialized
with:

   value -= value

   with value being undefined.
   In this case LLVM replace the operation with an assignment to NaN.

   Cc: 19.1 19.2 <mesa-stable@lists.freedesktop.org>
   Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111241
   Reviewed-by: Marek Olšák <marek.olsak@amd.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4048 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-09-02 23:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 18:06 [Bug 111241] Shadertoy shader causing hang bugzilla-daemon
2019-08-08 21:34 ` bugzilla-daemon
2019-08-09  0:15 ` bugzilla-daemon
2019-08-09 16:22 ` bugzilla-daemon
2019-08-09 16:22 ` bugzilla-daemon
2019-08-09 16:22 ` bugzilla-daemon
2019-08-14 12:56 ` bugzilla-daemon
2019-08-29 23:57 ` bugzilla-daemon
2019-08-30  0:05 ` bugzilla-daemon
2019-08-30  0:06 ` bugzilla-daemon
2019-08-30  0:11 ` bugzilla-daemon
2019-08-30 11:56 ` bugzilla-daemon
2019-08-30 23:57 ` bugzilla-daemon
2019-09-02 23:47 ` bugzilla-daemon [this message]
2019-09-03 12:00 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-111241-502-E6PgZpRYJw@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox