aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Analysis/BasicAliasAnalysis.cpp
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2021-03-22 16:45:54 -0400
committerSanjay Patel <spatel@rotateright.com>2021-03-22 16:49:21 -0400
commit27ae17a6b0145a559c501c35ded0ab4e9dd69e8e (patch)
tree3c1729cea64fb4bb9eadd92935c9da97c23795b5 /llvm/lib/Analysis/BasicAliasAnalysis.cpp
parent424bf5d8918f6356f1b8e99205c5fc8b4783ca22 (diff)
downloadllvm-27ae17a6b0145a559c501c35ded0ab4e9dd69e8e.zip
llvm-27ae17a6b0145a559c501c35ded0ab4e9dd69e8e.tar.gz
llvm-27ae17a6b0145a559c501c35ded0ab4e9dd69e8e.tar.bz2
[SimplifyCFG] use profile metadata to refine merging branch conditions
This is one step towards solving: https://llvm.org/PR49336 In that example, we disregard the recommended usage of builtin_expect, so an expensive (unpredictable) branch is folded into another branch that is guarding it. Here, we read the profile metadata to see if the 1st (predecessor) condition is likely to cause execution to bypass the 2nd (successor) condition before merging conditions by using logic ops. Differential Revision: https://reviews.llvm.org/D98898
Diffstat (limited to 'llvm/lib/Analysis/BasicAliasAnalysis.cpp')
0 files changed, 0 insertions, 0 deletions