summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Analysis/BasicAliasAnalysis.cpp
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2004-06-19 07:40:14 +0000
committerChris Lattner <sabre@nondot.org>2004-06-19 07:40:14 +0000
commita52ab6f57fb0bf04151c7eccb5219dd12cceea05 (patch)
tree15b25b61418fcbce92aac0f2805c8b25fa7fed12 /llvm/lib/Analysis/BasicAliasAnalysis.cpp
parentb2b151d2975d9712f35aad25cd11563216dca898 (diff)
downloadbcm5719-llvm-a52ab6f57fb0bf04151c7eccb5219dd12cceea05.tar.gz
bcm5719-llvm-a52ab6f57fb0bf04151c7eccb5219dd12cceea05.zip
Do not let the numbering of PHI nodes placed in the function depend on
non-deterministic things like the ordering of blocks in the dominance frontier of a BB. Unfortunately, I don't know of a better way to solve this problem than to explicitly sort the BB's in function-order before processing them. This is guaranteed to slow the pass down a bit, but is absolutely necessary to get usable diffs between two different tools executing the mem2reg or scalarrepl pass. Before this, bazillions of spurious diff failures occurred all over the place due to the different order of processing PHIs: - %tmp.111 = getelementptr %struct.Connector_struct* %upcon.0.0, uint 0, uint 0 + %tmp.111 = getelementptr %struct.Connector_struct* %upcon.0.1, uint 0, uint 0 Now, the diffs match. llvm-svn: 14244
Diffstat (limited to 'llvm/lib/Analysis/BasicAliasAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud