summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/CFIInstrInserter.cpp
diff options
context:
space:
mode:
authorDavide Italiano <davide@freebsd.org>2018-05-11 15:45:36 +0000
committerDavide Italiano <davide@freebsd.org>2018-05-11 15:45:36 +0000
commit6e1f7bf316424f3b3af108db4911c09cb24c421c (patch)
treee082ae2c2be4d0207c1345eaeb9e4a0558e9f6e7 /llvm/lib/CodeGen/CFIInstrInserter.cpp
parent0f2a48c1ae6d982c7245efd4ceb0673ae1387b90 (diff)
downloadbcm5719-llvm-6e1f7bf316424f3b3af108db4911c09cb24c421c.tar.gz
bcm5719-llvm-6e1f7bf316424f3b3af108db4911c09cb24c421c.zip
[Reassociate] Prevent infinite loops when processing PHIs.
Phi nodes can reside in live blocks but one of their incoming arguments can come from a dead block. Dead blocks and reassociate don't play nice together. In fact, reassociate performs an RPO as a first step to avoid processing dead blocks. The reason why Reassociate might not fixpoint when examining dead blocks is that the following: %xor0 = xor i16 %xor1, undef %xor1 = xor i16 %xor0, undef is perfectly valid LLVM IR (if it appears in a dead block), so the worklist algorithm keeps pushing the two instructions for reexamination. Note that this is not Reassociate fault, at least not entirely. It's llvm that has a weird definition of dominance. Fixes PR37390. llvm-svn: 332100
Diffstat (limited to 'llvm/lib/CodeGen/CFIInstrInserter.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud