diff options
| author | Tobias Grosser <tobias@grosser.es> | 2015-12-14 15:05:37 +0000 |
|---|---|---|
| committer | Tobias Grosser <tobias@grosser.es> | 2015-12-14 15:05:37 +0000 |
| commit | f4f6870ff22b3acd45006d6da685a23c03fc4b1b (patch) | |
| tree | 0a1ff336e4b4d001423434cc86ecc372c2264fda /lldb/packages/Python/lldbsuite/test/python_api/interpreter | |
| parent | 1e6e3c60b4d5263e641cef815a7dda7c9df840e7 (diff) | |
| download | bcm5719-llvm-f4f6870ff22b3acd45006d6da685a23c03fc4b1b.tar.gz bcm5719-llvm-f4f6870ff22b3acd45006d6da685a23c03fc4b1b.zip | |
Revert "Always treat scalar writes as MUST_WRITEs"
This reverts commit r255471.
Johannes raised in the post-commit review of r255471 the concern that PHI
writes in non-affine regions with two exiting blocks are not really MUST_WRITE,
but we just know that at least one out of the set of all possible PHI writes
will be executed. Modeling all PHI nodes as MUST_WRITEs is probably save, but
adding the needed documentation for such a special case is probably not worth
the effort. Michael will be proposing a new patch that ensures only a single
PHI_WRITE is created for non-affine regions, which - besides other benefits -
should also allow us to use a single well-defined MUST_WRITE for such PHI
writes.
(This is not a full revert, but the condition and documentation have been
slightly extended)
llvm-svn: 255503
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/interpreter')
0 files changed, 0 insertions, 0 deletions
