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 not 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 = 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.
I tested with a slightly older version of llvm I had locally that was based on llvm git from june, and the same behaviour occurs. It could be a radeonsi bug introduced in the llvm asm generation or an llvm bug uncovered by a change in that asm. I filled a bug on the llvm side as it's likely involved: https://bugs.llvm.org/show_bug.cgi?id=36704
Can you do a bisect between Mesa-17.2 and Mesa-17.3, using the same LLVM-5.0.1 ?
Patrick Rudolph bisected the radeonsi regression to: 2f4705afde707e8eb41b9414c25df91aa1ea2fb3 Checking the attached TGSI, it seems the lighting constants were not declared properly (which is illegal), and in conjunction with the behaviour introduced by this commit (which is legal), it caused the shader to never stop. The bug was thus a nine bug. Patch sent to the mailing list: https://lists.freedesktop.org/archives/mesa-dev/2018-April/190803.html
Patch pushed: https://cgit.freedesktop.org/mesa/mesa/commit/?id=39240926cd45519f35a6fa576c387f727b057aa1
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.