summaryrefslogtreecommitdiffstats
path: root/llvm/test/CodeGen/R600/fmax.ll
diff options
context:
space:
mode:
authorShuxin Yang <shuxin.llvm@gmail.com>2013-11-11 22:00:23 +0000
committerShuxin Yang <shuxin.llvm@gmail.com>2013-11-11 22:00:23 +0000
commit3168ab337635b6ed5a279cd432f95dc3da17fb2c (patch)
tree2373aff4207da3c37ad75b0eddf24d79c6a54f22 /llvm/test/CodeGen/R600/fmax.ll
parent8f1caeb0e187250cf96bdee3013c7a6f16ac2c6f (diff)
downloadbcm5719-llvm-3168ab337635b6ed5a279cd432f95dc3da17fb2c.tar.gz
bcm5719-llvm-3168ab337635b6ed5a279cd432f95dc3da17fb2c.zip
Fix PR17952.
The symptom is that an assertion is triggered. The assertion was added by me to detect the situation when value is propagated from dead blocks. (We can certainly get rid of assertion; it is safe to do so, because propagating value from dead block to alive join node is certainly ok.) The root cause of this bug is : edge-splitting is conducted on the fly, the edge being split could be a dead edge, therefore the block that split the critial edge needs to be flagged "dead" as well. There are 3 ways to fix this bug: 1) Get rid of the assertion as I mentioned eariler 2) When an dead edge is split, flag the inserted block "dead". 3) proactively split the critical edges connecting dead and live blocks when new dead blocks are revealed. This fix go for 3) with additional 2 LOC. Testing case was added by Rafael the other day. llvm-svn: 194424
Diffstat (limited to 'llvm/test/CodeGen/R600/fmax.ll')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud