All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103142] R600g+sb: optimizer apparently stuck in an endless loop
Date: Sat, 07 Oct 2017 22:37:27 +0000	[thread overview]
Message-ID: <bug-103142-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 103142
           Summary: R600g+sb: optimizer apparently stuck in an endless
                    loop
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: gw.fossdev@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Created attachment 134738
  --> https://bugs.freedesktop.org/attachment.cgi?id=134738&action=edit
TGSI, byte code and logging output

With sb enabled some shaders apparently trigger an endless loops in the sb
optimizer. 

The attached TGSI and log of a shader triggering this behaviour comes from the
Unreal Editor version 4.17.1,  

The log was created with 

  #define PSC_DEBUG 1 

in src/gallium/drivers/r600/sb_sched.cpp

The problem is probably related to the "FIXME rework this loop" on line 1808 in
the same file, and I also have the impression that it has something to do with
MULADD when the sources are a mix of CONST and IMM.

I'd try to fix it myself, but right now I don't really have a clue how to
approach this bug.

best, 
Gert

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

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

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

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

             reply	other threads:[~2017-10-07 22:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-07 22:37 bugzilla-daemon [this message]
2017-10-09  7:51 ` [Bug 103142] R600g+sb: optimizer apparently stuck in an endless loop bugzilla-daemon
2017-10-09 19:54 ` bugzilla-daemon
2017-10-10 10:23 ` bugzilla-daemon
2017-10-10 10:25 ` bugzilla-daemon
2017-11-09 15:33 ` bugzilla-daemon
2017-11-09 17:07 ` bugzilla-daemon
2018-02-07 17:28 ` bugzilla-daemon
2018-02-07 17:32 ` 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-103142-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.