From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105442] Hang when running nine ff lighting shader Date: Sun, 11 Mar 2018 22:25:23 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1947510449==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 405496E0B3 for ; Sun, 11 Mar 2018 22:25:23 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1947510449== Content-Type: multipart/alternative; boundary="15208071230.B276A30.1522" Content-Transfer-Encoding: 7bit --15208071230.B276A30.1522 Date: Sun, 11 Mar 2018 22:25:23 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105442 Bug ID: 105442 Summary: Hang when running nine ff lighting shader Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: davyaxel0@gmail.com QA Contact: dri-devel@lists.freedesktop.org Created attachment 138005 --> https://bugs.freedesktop.org/attachment.cgi?id=3D138005&action=3Dedit tgsi, llvm and asm Any app/game running nine ff shader with lighting on hangs on my RX480 with mesa git/llvm 5.0.1 The shader works well under llvmpipe and works with mesa 17.2. sisched or n= ot doesn't make a difference. The shader features a loop over the lights. When the lights is the last (a constant is set to 1) the loop should stop. The constants start at pos 32 and are then incremented by 8. I suspect comparing the correct and the fauly generated shader that the increment happens at the beginning of the loop instead of at the end: The faulty shader has: s_branch BB0_2 ; BF820000 v_add_f32_e32 v20, 0x41000000, v20 ; 022828FF 41000000 According to the s_branch encoding, it should do PC =3D PC + 4 Does that mean it is noop ? Or could it be that it jumps in the middle of the the two word following instruction ? Thus causing the constant to be interpreted as an instruction= ? It could be an llvm bug or a mesa bug, thus I'm posting here in any case. --=20 You are receiving this mail because: You are the assignee for the bug.= --15208071230.B276A30.1522 Date: Sun, 11 Mar 2018 22:25:23 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 105442
Summary Hang when running nine ff lighting shader
Product Mesa
Version git
Hardware Other
OS All
Status NEW
Severity normal
Priority medium
Component Drivers/Gallium/radeonsi
Assignee dri-devel@lists.freedesktop.org
Reporter davyaxel0@gmail.com
QA Contact dri-devel@lists.freedesktop.org

Created attachment 138005=
 [details]
tgsi, llvm and asm

Any app/game running nine ff shader with lighting on hangs on my RX480 with
mesa git/llvm 5.0.1

The shader works well under llvmpipe and works with mesa 17.2. sisched or n=
ot
doesn't make a difference.

The shader features a loop over the lights. When the lights is the last (a
constant is set to 1) the loop should stop.

The constants start at pos 32 and are then incremented by 8.

I suspect comparing the correct and the fauly generated shader that the
increment happens at the beginning of the loop instead of at the end:

The faulty shader has:
s_branch BB0_2                                        ; BF820000
v_add_f32_e32 v20, 0x41000000, v20                    ; 022828FF 41000000

According to the s_branch encoding, it should do PC =3D PC + 4

Does that mean it is noop ?
Or could it be that it jumps in the middle of the the two word following
instruction ? Thus causing the constant to be interpreted as an instruction=
 ?

It could be an llvm bug or a mesa bug, thus I'm posting here in any case.
        


You are receiving this mail because:
  • You are the assignee for the bug.
= --15208071230.B276A30.1522-- --===============1947510449== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1947510449==--