aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/IR/Module.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2014-02-25 21:54:50 +0000
committerChandler Carruth <chandlerc@gmail.com>2014-02-25 21:54:50 +0000
commit7b8e11240775d4c8cbdd2e63ef7df5a41ddbd753 (patch)
tree24b31e98c3350f59707e238170158aaf574151b8 /llvm/lib/IR/Module.cpp
parentfd0d86c3223ad1bcca1e822dcf52d9aa030c3a49 (diff)
downloadllvm-7b8e11240775d4c8cbdd2e63ef7df5a41ddbd753.zip
llvm-7b8e11240775d4c8cbdd2e63ef7df5a41ddbd753.tar.gz
llvm-7b8e11240775d4c8cbdd2e63ef7df5a41ddbd753.tar.bz2
[reassociate] Switch two std::sort calls into std::stable_sort calls as
their inputs come from std::stable_sort and they are not total orders. I'm not a huge fan of this, but the really bad std::stable_sort is right at the beginning of Reassociate. After we commit to stable-sort based consistent respect of source order, the downstream sorts shouldn't undo that unless they have a total order or they are used in an order-insensitive way. Neither appears to be true for these cases. I don't have particularly good test cases, but this jumped out by inspection when looking for output instability in this pass due to changes in the ordering of std::sort. llvm-svn: 202196
Diffstat (limited to 'llvm/lib/IR/Module.cpp')
0 files changed, 0 insertions, 0 deletions