HomePhabricator

[Analysis] Make LocationSizes carry an 'imprecise' bit

Description

[Analysis] Make LocationSizes carry an 'imprecise' bit

There are places where we need to merge multiple LocationSizes of
different sizes into one, and get a sensible result.

There are other places where we want to optimize aggressively based on
the value of a LocationSizes (e.g. how can a store of four bytes be to
an area of storage that's only two bytes large?)

This patch makes LocationSize hold an 'imprecise' bit to note whether
the LocationSize can be treated as an upper-bound and lower-bound for
the size of a location, or just an upper-bound.

This concludes the series of patches leading up to this. The most recent
of which is r344108.

Fixes PR36228.

Differential Revision: https://reviews.llvm.org/D44748

Details

Committed
gbivOct 9 2018, 11:39 PM
Differential Revision
D44748: Track whether the size of a MemoryLocation is precise
Parents
rL344113: [NFC] Make a variable const
Branches
Unknown
Tags
Unknown