aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/CodeGen/CodeGenFunction.cpp
diff options
context:
space:
mode:
authorFlorian Hahn <flo@fhahn.com>2020-04-17 15:30:00 +0100
committerFlorian Hahn <flo@fhahn.com>2020-04-17 15:38:23 +0100
commitc245d3e033a58582475c3d749085f47a9ab0dda1 (patch)
treeb3d53089454bf2aa0accf49fb6a92bc31576dc13 /clang/lib/CodeGen/CodeGenFunction.cpp
parenta8e4b7a5504196fc920126fb1e71d221e3879545 (diff)
downloadllvm-c245d3e033a58582475c3d749085f47a9ab0dda1.zip
llvm-c245d3e033a58582475c3d749085f47a9ab0dda1.tar.gz
llvm-c245d3e033a58582475c3d749085f47a9ab0dda1.tar.bz2
[ValueLattice] Steal bits from Tag to track range extensions (NFC).
Users of ValueLatticeElement currently have to ensure constant ranges are not extended indefinitely. For example, in SCCP, mergeIn goes to overdefined if a constantrange value is repeatedly merged with larger constantranges. This is a simple form of widening. In some cases, this leads to an unnecessary loss of information and things can be improved by allowing a small number of extensions in the hope that a fixed point is reached after a small number of steps. To make better decisions about widening, it is helpful to keep track of the number of range extensions. That state is tied directly to a concrete ValueLatticeElement and some unused bits in the class can be used. The current patch preserves the existing behavior by default: CheckWiden defaults to false and if CheckWiden is true, a single change to the range is allowed. Follow-up patches will slightly increase the threshold for widening. Reviewers: efriedma, davide, mssimpso Reviewed By: efriedma Differential Revision: https://reviews.llvm.org/D78145
Diffstat (limited to 'clang/lib/CodeGen/CodeGenFunction.cpp')
0 files changed, 0 insertions, 0 deletions