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 102387] Assertion failure with UE4Editor and sb enabled
Date: Thu, 24 Aug 2017 12:50:15 +0000	[thread overview]
Message-ID: <bug-102387-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 102387
           Summary: Assertion failure with UE4Editor and sb enabled
           Product: Mesa
           Version: git
          Hardware: Other
                OS: 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 133745
  --> https://bugs.freedesktop.org/attachment.cgi?id=133745&action=edit
TGSI and byte code of the buggy shader

When running UE4Editor (4.17) on BARTS with -opengl3 and mesa (1e696b9) is
compiled in debug mode I get the following assertion failure on one shader
(attached), that then leads to UE4Editor shutting down: 

  error at : MUL_IEEE     R17.x.5F@R124.x,    R14.x.5F@R124.x, R90.x.22||F@R2.w
   : expected operand value R90.x.22||F@R2.w, gpr contains t39||FP@R2.w
  sb/sb_ra_checker.cpp:46:run: Assertion `sh.errors.empty()' failed.

Sometimes it happens right away, when loading the assets, sometimes I have to
load a specific level. I guess it depends on what assets are actually
displayed.  

If I disable the assertion then I can use UE4Editor (I still need to add a
patch to work around to a problem introduced by another shader that for some
bug in UE4 exceeds the limits of the GPRs, but this has nothing to do which
this assertion failure).

Best, 
Gert

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

[-- Attachment #1.2: Type: text/html, Size: 3364 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-08-24 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 12:50 bugzilla-daemon [this message]
2017-08-24 12:50 ` [Bug 102387] Assertion failure with UE4Editor and sb enabled bugzilla-daemon
2019-09-18 19:24 ` 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-102387-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox