diff options
| author | Florian Hahn <florian.hahn@arm.com> | 2018-02-27 09:34:51 +0000 |
|---|---|---|
| committer | Florian Hahn <florian.hahn@arm.com> | 2018-02-27 09:34:51 +0000 |
| commit | 1807c516c77eb2b66ee84cba56435897c913812d (patch) | |
| tree | 48d90d6bc49bd7a4f1ca7b427dcb373cd286c782 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp | |
| parent | f9b3c67956ef81342ca748398ca6c6aacd88d7ca (diff) | |
| download | bcm5719-llvm-1807c516c77eb2b66ee84cba56435897c913812d.tar.gz bcm5719-llvm-1807c516c77eb2b66ee84cba56435897c913812d.zip | |
[NewGVN] Update phi-of-ops def block when updating existing ValuePHI.
In case we update a ValuePHI node created earlier, we could update it
based on a different OpPHI which could be in a different block.
We need to update the TempToBlock mapping reflecting the new block,
otherwise we would end up placing the new phi node in a wrong block.
This problem is exposed by the test case in
https://bugs.llvm.org/show_bug.cgi?id=36504.
This patch fixes a slightly simpler problem than in the bug report. In
the bug's re-producer, the additional problem is that we are re-using a
ValuePHI node with to few incoming values for the new OpPHI. If this
patch makes sense, I will follow it up with a patch that creates a new
PHI node if the existing PHI node has a different number of incoming
values.
Reviewers: davide, dberlin
Reviewed By: dberlin
Differential Revision: https://reviews.llvm.org/D43770
llvm-svn: 326181
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
