2008-06-02 01:18:21 +00:00
|
|
|
//===- llvm/Analysis/ValueTracking.h - Walk computations --------*- C++ -*-===//
|
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// This file contains routines that help analyze properties that chains of
|
|
|
|
// computations have.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#ifndef LLVM_ANALYSIS_VALUETRACKING_H
|
|
|
|
#define LLVM_ANALYSIS_VALUETRACKING_H
|
|
|
|
|
2011-07-13 10:26:04 +00:00
|
|
|
#include "llvm/ADT/ArrayRef.h"
|
2010-11-29 18:16:10 +00:00
|
|
|
#include "llvm/Support/DataTypes.h"
|
2008-06-26 00:31:12 +00:00
|
|
|
|
2008-06-02 01:18:21 +00:00
|
|
|
namespace llvm {
|
|
|
|
class Value;
|
2008-06-16 12:48:21 +00:00
|
|
|
class Instruction;
|
2008-06-02 01:18:21 +00:00
|
|
|
class APInt;
|
2012-10-08 16:38:25 +00:00
|
|
|
class DataLayout;
|
2012-02-05 02:29:43 +00:00
|
|
|
class StringRef;
|
2012-03-31 18:14:00 +00:00
|
|
|
class MDNode;
|
2015-01-04 12:03:27 +00:00
|
|
|
class AssumptionCache;
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
class DominatorTree;
|
2013-09-24 16:37:51 +00:00
|
|
|
class TargetLibraryInfo;
|
2012-03-31 18:14:00 +00:00
|
|
|
|
2014-05-14 21:14:37 +00:00
|
|
|
/// Determine which bits of V are known to be either zero or one and return
|
|
|
|
/// them in the KnownZero/KnownOne bit sets.
|
2009-09-08 00:06:16 +00:00
|
|
|
///
|
|
|
|
/// This function is defined on values with integer type, values with pointer
|
2015-03-10 02:37:25 +00:00
|
|
|
/// type, and vectors of integers. In the case
|
2014-05-14 08:00:07 +00:00
|
|
|
/// where V is a vector, the known zero and known one values are the
|
2009-09-08 00:06:16 +00:00
|
|
|
/// same width as the vector element, and the bit is set only if it is true
|
|
|
|
/// for all of the elements in the vector.
|
2015-01-04 12:03:27 +00:00
|
|
|
void computeKnownBits(Value *V, APInt &KnownZero, APInt &KnownOne,
|
2015-03-10 02:37:25 +00:00
|
|
|
const DataLayout &DL, unsigned Depth = 0,
|
2015-01-04 12:03:27 +00:00
|
|
|
AssumptionCache *AC = nullptr,
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
const Instruction *CxtI = nullptr,
|
|
|
|
const DominatorTree *DT = nullptr);
|
2014-06-19 16:50:16 +00:00
|
|
|
/// Compute known bits from the range metadata.
|
|
|
|
/// \p KnownZero the set of bits that are known to be zero
|
|
|
|
void computeKnownBitsFromRangeMetadata(const MDNode &Ranges,
|
|
|
|
APInt &KnownZero);
|
2012-03-31 18:14:00 +00:00
|
|
|
|
2011-01-25 09:38:29 +00:00
|
|
|
/// ComputeSignBit - Determine whether the sign bit is known to be zero or
|
2014-05-14 21:14:37 +00:00
|
|
|
/// one. Convenience wrapper around computeKnownBits.
|
2011-01-25 09:38:29 +00:00
|
|
|
void ComputeSignBit(Value *V, bool &KnownZero, bool &KnownOne,
|
2015-03-10 02:37:25 +00:00
|
|
|
const DataLayout &DL, unsigned Depth = 0,
|
2015-01-04 12:03:27 +00:00
|
|
|
AssumptionCache *AC = nullptr,
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
const Instruction *CxtI = nullptr,
|
|
|
|
const DominatorTree *DT = nullptr);
|
2011-01-25 09:38:29 +00:00
|
|
|
|
2012-12-13 03:37:24 +00:00
|
|
|
/// isKnownToBeAPowerOfTwo - Return true if the given value is known to have
|
|
|
|
/// exactly one bit set when defined. For vectors return true if every
|
|
|
|
/// element is known to be a power of two when defined. Supports values with
|
|
|
|
/// integer or pointer type and vectors of integers. If 'OrZero' is set then
|
|
|
|
/// returns true if the given value is either a power of two or zero.
|
2015-03-10 02:37:25 +00:00
|
|
|
bool isKnownToBeAPowerOfTwo(Value *V, const DataLayout &DL,
|
|
|
|
bool OrZero = false, unsigned Depth = 0,
|
2015-01-04 12:03:27 +00:00
|
|
|
AssumptionCache *AC = nullptr,
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
const Instruction *CxtI = nullptr,
|
|
|
|
const DominatorTree *DT = nullptr);
|
2011-01-25 09:38:29 +00:00
|
|
|
|
|
|
|
/// isKnownNonZero - Return true if the given value is known to be non-zero
|
|
|
|
/// when defined. For vectors return true if every element is known to be
|
|
|
|
/// non-zero when defined. Supports values with integer or pointer type and
|
|
|
|
/// vectors of integers.
|
2015-03-10 02:37:25 +00:00
|
|
|
bool isKnownNonZero(Value *V, const DataLayout &DL, unsigned Depth = 0,
|
|
|
|
AssumptionCache *AC = nullptr,
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
const Instruction *CxtI = nullptr,
|
|
|
|
const DominatorTree *DT = nullptr);
|
2011-01-25 09:38:29 +00:00
|
|
|
|
2008-06-02 01:29:46 +00:00
|
|
|
/// MaskedValueIsZero - Return true if 'V & Mask' is known to be zero. We use
|
|
|
|
/// this predicate to simplify operations downstream. Mask is known to be
|
|
|
|
/// zero for bits that V cannot have.
|
2009-09-08 00:06:16 +00:00
|
|
|
///
|
|
|
|
/// This function is defined on values with integer type, values with pointer
|
2015-03-10 02:37:25 +00:00
|
|
|
/// type, and vectors of integers. In the case
|
2009-09-08 00:06:16 +00:00
|
|
|
/// where V is a vector, the mask, known zero, and known one values are the
|
|
|
|
/// same width as the vector element, and the bit is set only if it is true
|
|
|
|
/// for all of the elements in the vector.
|
2015-03-10 02:37:25 +00:00
|
|
|
bool MaskedValueIsZero(Value *V, const APInt &Mask, const DataLayout &DL,
|
|
|
|
unsigned Depth = 0, AssumptionCache *AC = nullptr,
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
const Instruction *CxtI = nullptr,
|
|
|
|
const DominatorTree *DT = nullptr);
|
2008-06-02 01:18:21 +00:00
|
|
|
|
|
|
|
/// ComputeNumSignBits - Return the number of times the sign bit of the
|
|
|
|
/// register is replicated into the other bits. We know that at least 1 bit
|
|
|
|
/// is always equal to the sign bit (itself), but other cases can give us
|
|
|
|
/// information. For example, immediately after an "ashr X, 2", we know that
|
|
|
|
/// the top 3 bits are all equal to each other, so we return 3.
|
|
|
|
///
|
|
|
|
/// 'Op' must have a scalar integer type.
|
|
|
|
///
|
2015-03-10 02:37:25 +00:00
|
|
|
unsigned ComputeNumSignBits(Value *Op, const DataLayout &DL,
|
2015-01-04 12:03:27 +00:00
|
|
|
unsigned Depth = 0, AssumptionCache *AC = nullptr,
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
const Instruction *CxtI = nullptr,
|
|
|
|
const DominatorTree *DT = nullptr);
|
2008-06-02 01:18:21 +00:00
|
|
|
|
2009-11-10 08:28:35 +00:00
|
|
|
/// ComputeMultiple - This function computes the integer multiple of Base that
|
|
|
|
/// equals V. If successful, it returns true and returns the multiple in
|
|
|
|
/// Multiple. If unsuccessful, it returns false. Also, if V can be
|
|
|
|
/// simplified to an integer, then the simplified V is returned in Val. Look
|
|
|
|
/// through sext only if LookThroughSExt=true.
|
2009-11-18 00:58:27 +00:00
|
|
|
bool ComputeMultiple(Value *V, unsigned Base, Value *&Multiple,
|
|
|
|
bool LookThroughSExt = false,
|
2009-11-10 08:28:35 +00:00
|
|
|
unsigned Depth = 0);
|
|
|
|
|
2008-06-02 01:29:46 +00:00
|
|
|
/// CannotBeNegativeZero - Return true if we can prove that the specified FP
|
|
|
|
/// value is never equal to -0.0.
|
|
|
|
///
|
|
|
|
bool CannotBeNegativeZero(const Value *V, unsigned Depth = 0);
|
2008-06-16 12:48:21 +00:00
|
|
|
|
2015-01-28 08:03:58 +00:00
|
|
|
/// CannotBeOrderedLessThanZero - Return true if we can prove that the
|
|
|
|
/// specified FP value is either a NaN or never less than 0.0.
|
|
|
|
///
|
|
|
|
bool CannotBeOrderedLessThanZero(const Value *V, unsigned Depth = 0);
|
|
|
|
|
2010-12-26 20:15:01 +00:00
|
|
|
/// isBytewiseValue - If the specified value can be set by repeating the same
|
|
|
|
/// byte in memory, return the i8 value that it is represented with. This is
|
|
|
|
/// true for all i8 values obviously, but is also true for i32 0, i32 -1,
|
|
|
|
/// i16 0xF0F0, double 0.0 etc. If the value can't be handled with a repeated
|
|
|
|
/// byte store (e.g. i16 0x1234), return null.
|
|
|
|
Value *isBytewiseValue(Value *V);
|
|
|
|
|
2010-05-28 16:06:09 +00:00
|
|
|
/// FindInsertedValue - Given an aggregrate and an sequence of indices, see if
|
2008-06-17 08:26:32 +00:00
|
|
|
/// the scalar value indexed is already around as a register, for example if
|
|
|
|
/// it were inserted directly into the aggregrate.
|
2008-06-16 13:28:31 +00:00
|
|
|
///
|
|
|
|
/// If InsertBefore is not null, this function will duplicate (modified)
|
|
|
|
/// insertvalues when a part of a nested struct is extracted.
|
2008-06-16 12:48:21 +00:00
|
|
|
Value *FindInsertedValue(Value *V,
|
2011-07-13 10:26:04 +00:00
|
|
|
ArrayRef<unsigned> idx_range,
|
2014-04-09 06:08:46 +00:00
|
|
|
Instruction *InsertBefore = nullptr);
|
2008-06-17 13:54:33 +00:00
|
|
|
|
2010-11-30 22:25:26 +00:00
|
|
|
/// GetPointerBaseWithConstantOffset - Analyze the specified pointer to see if
|
|
|
|
/// it can be expressed as a base pointer plus a constant offset. Return the
|
|
|
|
/// base and offset to the caller.
|
|
|
|
Value *GetPointerBaseWithConstantOffset(Value *Ptr, int64_t &Offset,
|
2015-03-10 02:37:25 +00:00
|
|
|
const DataLayout &DL);
|
2010-11-30 23:05:20 +00:00
|
|
|
static inline const Value *
|
|
|
|
GetPointerBaseWithConstantOffset(const Value *Ptr, int64_t &Offset,
|
2015-03-10 02:37:25 +00:00
|
|
|
const DataLayout &DL) {
|
|
|
|
return GetPointerBaseWithConstantOffset(const_cast<Value *>(Ptr), Offset,
|
|
|
|
DL);
|
2010-11-30 23:05:20 +00:00
|
|
|
}
|
2010-11-30 22:25:26 +00:00
|
|
|
|
2012-02-05 02:29:43 +00:00
|
|
|
/// getConstantStringInfo - This function computes the length of a
|
2009-03-13 04:39:26 +00:00
|
|
|
/// null-terminated C string pointed to by V. If successful, it returns true
|
2012-02-05 02:29:43 +00:00
|
|
|
/// and returns the string in Str. If unsuccessful, it returns false. This
|
|
|
|
/// does not include the trailing nul character by default. If TrimAtNul is
|
|
|
|
/// set to false, then this returns any trailing nul characters as well as any
|
|
|
|
/// other characters that come after it.
|
|
|
|
bool getConstantStringInfo(const Value *V, StringRef &Str,
|
|
|
|
uint64_t Offset = 0, bool TrimAtNul = true);
|
|
|
|
|
2010-03-05 06:58:57 +00:00
|
|
|
/// GetStringLength - If we can compute the length of the string pointed to by
|
|
|
|
/// the specified pointer, return 'len+1'. If we can't, return 0.
|
|
|
|
uint64_t GetStringLength(Value *V);
|
2010-12-15 20:02:24 +00:00
|
|
|
|
|
|
|
/// GetUnderlyingObject - This method strips off any GEP address adjustments
|
|
|
|
/// and pointer casts from the specified value, returning the original object
|
|
|
|
/// being addressed. Note that the returned value has pointer type if the
|
|
|
|
/// specified value does. If the MaxLookup value is non-zero, it limits the
|
|
|
|
/// number of instructions to be stripped off.
|
2015-03-10 02:37:25 +00:00
|
|
|
Value *GetUnderlyingObject(Value *V, const DataLayout &DL,
|
2011-01-24 18:53:32 +00:00
|
|
|
unsigned MaxLookup = 6);
|
2015-03-10 02:37:25 +00:00
|
|
|
static inline const Value *GetUnderlyingObject(const Value *V,
|
|
|
|
const DataLayout &DL,
|
|
|
|
unsigned MaxLookup = 6) {
|
|
|
|
return GetUnderlyingObject(const_cast<Value *>(V), DL, MaxLookup);
|
2010-12-15 20:02:24 +00:00
|
|
|
}
|
|
|
|
|
2012-05-10 18:57:38 +00:00
|
|
|
/// GetUnderlyingObjects - This method is similar to GetUnderlyingObject
|
|
|
|
/// except that it can look through phi and select instructions and return
|
|
|
|
/// multiple objects.
|
2015-03-10 02:37:25 +00:00
|
|
|
void GetUnderlyingObjects(Value *V, SmallVectorImpl<Value *> &Objects,
|
|
|
|
const DataLayout &DL, unsigned MaxLookup = 6);
|
2012-05-10 18:57:38 +00:00
|
|
|
|
2011-06-27 04:20:45 +00:00
|
|
|
/// onlyUsedByLifetimeMarkers - Return true if the only users of this pointer
|
|
|
|
/// are lifetime markers.
|
|
|
|
bool onlyUsedByLifetimeMarkers(const Value *V);
|
|
|
|
|
2011-12-14 23:49:11 +00:00
|
|
|
/// isSafeToSpeculativelyExecute - Return true if the instruction does not
|
|
|
|
/// have any effects besides calculating the result and does not have
|
|
|
|
/// undefined behavior.
|
|
|
|
///
|
|
|
|
/// This method never returns true for an instruction that returns true for
|
|
|
|
/// mayHaveSideEffects; however, this method also does some other checks in
|
|
|
|
/// addition. It checks for undefined behavior, like dividing by zero or
|
|
|
|
/// loading from an invalid pointer (but not for undefined results, like a
|
|
|
|
/// shift with a shift amount larger than the width of the result). It checks
|
|
|
|
/// for malloc and alloca because speculatively executing them might cause a
|
|
|
|
/// memory leak. It also returns false for instructions related to control
|
|
|
|
/// flow, specifically terminators and PHI nodes.
|
|
|
|
///
|
|
|
|
/// This method only looks at the instruction itself and its operands, so if
|
|
|
|
/// this method returns true, it is safe to move the instruction as long as
|
|
|
|
/// the correct dominance relationships for the operands and users hold.
|
|
|
|
/// However, this method can return true for instructions that read memory;
|
|
|
|
/// for such instructions, moving them may change the resulting value.
|
2015-03-10 02:37:25 +00:00
|
|
|
bool isSafeToSpeculativelyExecute(const Value *V);
|
2011-12-14 23:49:11 +00:00
|
|
|
|
2013-01-31 02:40:59 +00:00
|
|
|
/// isKnownNonNull - Return true if this pointer couldn't possibly be null by
|
|
|
|
/// its definition. This returns true for allocas, non-extern-weak globals
|
|
|
|
/// and byval arguments.
|
2014-04-09 06:08:46 +00:00
|
|
|
bool isKnownNonNull(const Value *V, const TargetLibraryInfo *TLI = nullptr);
|
2013-01-31 02:40:59 +00:00
|
|
|
|
Make use of @llvm.assume in ValueTracking (computeKnownBits, etc.)
This change, which allows @llvm.assume to be used from within computeKnownBits
(and other associated functions in ValueTracking), adds some (optional)
parameters to computeKnownBits and friends. These functions now (optionally)
take a "context" instruction pointer, an AssumptionTracker pointer, and also a
DomTree pointer, and most of the changes are just to pass this new information
when it is easily available from InstSimplify, InstCombine, etc.
As explained below, the significant conceptual change is that known properties
of a value might depend on the control-flow location of the use (because we
care that the @llvm.assume dominates the use because assumptions have
control-flow dependencies). This means that, when we ask if bits are known in a
value, we might get different answers for different uses.
The significant changes are all in ValueTracking. Two main changes: First, as
with the rest of the code, new parameters need to be passed around. To make
this easier, I grouped them into a structure, and I made internal static
versions of the relevant functions that take this structure as a parameter. The
new code does as you might expect, it looks for @llvm.assume calls that make
use of the value we're trying to learn something about (often indirectly),
attempts to pattern match that expression, and uses the result if successful.
By making use of the AssumptionTracker, the process of finding @llvm.assume
calls is not expensive.
Part of the structure being passed around inside ValueTracking is a set of
already-considered @llvm.assume calls. This is to prevent a query using, for
example, the assume(a == b), to recurse on itself. The context and DT params
are used to find applicable assumptions. An assumption needs to dominate the
context instruction, or come after it deterministically. In this latter case we
only handle the specific case where both the assumption and the context
instruction are in the same block, and we need to exclude assumptions from
being used to simplify their own ephemeral values (those which contribute only
to the assumption) because otherwise the assumption would prove its feeding
comparison trivial and would be removed.
This commit adds the plumbing and the logic for a simple masked-bit propagation
(just enough to write a regression test). Future commits add more patterns
(and, correspondingly, more regression tests).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@217342 91177308-0d34-0410-b5e6-96231b3b80d8
2014-09-07 18:57:58 +00:00
|
|
|
/// Return true if it is valid to use the assumptions provided by an
|
|
|
|
/// assume intrinsic, I, at the point in the control-flow identified by the
|
|
|
|
/// context instruction, CxtI.
|
|
|
|
bool isValidAssumeForContext(const Instruction *I, const Instruction *CxtI,
|
|
|
|
const DominatorTree *DT = nullptr);
|
|
|
|
|
2015-01-02 07:29:43 +00:00
|
|
|
enum class OverflowResult { AlwaysOverflows, MayOverflow, NeverOverflows };
|
|
|
|
OverflowResult computeOverflowForUnsignedMul(Value *LHS, Value *RHS,
|
2015-03-10 02:37:25 +00:00
|
|
|
const DataLayout &DL,
|
2015-01-04 12:03:27 +00:00
|
|
|
AssumptionCache *AC,
|
2015-01-02 07:29:43 +00:00
|
|
|
const Instruction *CxtI,
|
|
|
|
const DominatorTree *DT);
|
2015-01-07 00:39:50 +00:00
|
|
|
OverflowResult computeOverflowForUnsignedAdd(Value *LHS, Value *RHS,
|
2015-03-10 02:37:25 +00:00
|
|
|
const DataLayout &DL,
|
2015-01-07 00:39:50 +00:00
|
|
|
AssumptionCache *AC,
|
|
|
|
const Instruction *CxtI,
|
|
|
|
const DominatorTree *DT);
|
2008-06-02 01:18:21 +00:00
|
|
|
} // end namespace llvm
|
|
|
|
|
|
|
|
#endif
|