Bug 102387 - Assertion failure with UE4Editor and sb enabled
Summary: Assertion failure with UE4Editor and sb enabled
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-24 12:50 UTC by Gert Wollny
Modified: 2019-09-18 19:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
TGSI and byte code of the offending shader (49.36 KB, text/plain)
2017-08-24 12:50 UTC, Gert Wollny
Details

Description Gert Wollny 2017-08-24 12:50:15 UTC
Created attachment 133745 [details]
TGSI and byte code of the offending  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
Comment 1 GitLab Migration User 2019-09-18 19:24:09 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/609.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.