summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
diff options
context:
space:
mode:
authorMatt Arsenault <Matthew.Arsenault@amd.com>2017-01-24 22:18:39 +0000
committerMatt Arsenault <Matthew.Arsenault@amd.com>2017-01-24 22:18:39 +0000
commitbf67cf7e4b42207e9e48b1de16d11c49a47279cc (patch)
tree6ebc099c1dcf5e95cf206a45b955b1040cdab276 /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
parentf1cf0278e8a90628eea80ace88f54f9035f3730d (diff)
downloadbcm5719-llvm-bf67cf7e4b42207e9e48b1de16d11c49a47279cc.tar.gz
bcm5719-llvm-bf67cf7e4b42207e9e48b1de16d11c49a47279cc.zip
AMDGPU: Remove spurious out branches after a kill
The sequence like this: v_cmpx_le_f32_e32 vcc, 0, v0 s_branch BB0_30 s_cbranch_execnz BB0_30 ; BB#29: exp null off, off, off, off done vm s_endpgm BB0_30: ; %endif110 is likely wrong. The s_branch instruction will unconditionally jump to BB0_30 and the skip block (exp done + endpgm) inserted for performing the kill instruction will never be executed. This results in a GPU hang with Star Ruler 2. The s_branch instruction is added during the "Control Flow Optimizer" pass which seems to re-organize the basic blocks, and we assume that SI_KILL_TERMINATOR is always the last instruction inside a basic block. Thus, after inserting a skip block we just go to the next BB without looking at the subsequent instructions after the kill, and the s_branch op is never removed. Instead, we should remove the unconditional out branches and let skip the two instructions if the exec mask is non-zero. This patch fixes the GPU hang and doesn't introduce any regressions with "make check". Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99019 Patch by Samuel Pitoiset <samuel.pitoiset@gmail.com> llvm-svn: 292985
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud