2003-09-30 18:37:50 +00:00
|
|
|
//===-- llvm/User.h - User class definition ---------------------*- C++ -*-===//
|
2005-04-21 20:19:05 +00:00
|
|
|
//
|
2003-10-20 20:19:47 +00:00
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
2007-12-29 19:59:42 +00:00
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
2005-04-21 20:19:05 +00:00
|
|
|
//
|
2003-10-20 20:19:47 +00:00
|
|
|
//===----------------------------------------------------------------------===//
|
2001-06-06 20:29:01 +00:00
|
|
|
//
|
2012-05-16 22:08:58 +00:00
|
|
|
// This class defines the interface that one who uses a Value must implement.
|
2001-06-06 20:29:01 +00:00
|
|
|
// Each instance of the Value class keeps track of what User's have handles
|
|
|
|
// to it.
|
|
|
|
//
|
2012-05-16 22:08:58 +00:00
|
|
|
// * Instructions are the largest class of Users.
|
2001-06-06 20:29:01 +00:00
|
|
|
// * Constants may be users of other constants (think arrays and stuff)
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
2013-01-10 00:45:19 +00:00
|
|
|
#ifndef LLVM_IR_USER_H
|
|
|
|
#define LLVM_IR_USER_H
|
2001-06-06 20:29:01 +00:00
|
|
|
|
2014-04-24 05:33:53 +00:00
|
|
|
#include "llvm/ADT/iterator.h"
|
2014-03-03 10:42:58 +00:00
|
|
|
#include "llvm/ADT/iterator_range.h"
|
2013-01-02 11:36:10 +00:00
|
|
|
#include "llvm/IR/Value.h"
|
2012-02-05 22:14:15 +00:00
|
|
|
#include "llvm/Support/ErrorHandling.h"
|
2001-06-06 20:29:01 +00:00
|
|
|
|
2003-11-11 22:41:34 +00:00
|
|
|
namespace llvm {
|
|
|
|
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief Compile-time customization of User operands.
|
|
|
|
///
|
|
|
|
/// Customizes operand-related allocators and accessors.
|
2008-05-10 08:32:32 +00:00
|
|
|
template <class>
|
|
|
|
struct OperandTraits;
|
|
|
|
|
2001-06-06 20:29:01 +00:00
|
|
|
class User : public Value {
|
2015-02-15 22:54:22 +00:00
|
|
|
User(const User &) = delete;
|
|
|
|
void *operator new(size_t) = delete;
|
2008-05-10 08:32:32 +00:00
|
|
|
template <unsigned>
|
|
|
|
friend struct HungoffOperandTraits;
|
2011-12-01 08:00:17 +00:00
|
|
|
virtual void anchor();
|
2001-07-07 08:36:50 +00:00
|
|
|
protected:
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief This is a pointer to the array of Uses for this User.
|
|
|
|
///
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
/// For nodes of fixed arity (e.g. a binary operator) this array will live
|
2009-02-21 01:09:07 +00:00
|
|
|
/// prefixed to some derived class instance. For nodes of resizable variable
|
|
|
|
/// arity (e.g. PHINodes, SwitchInst etc.), this memory will be dynamically
|
|
|
|
/// allocated and should be destroyed by the classes' virtual dtor.
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
Use *OperandList;
|
|
|
|
|
2008-05-15 01:23:11 +00:00
|
|
|
void *operator new(size_t s, unsigned Us);
|
2011-07-18 04:54:35 +00:00
|
|
|
User(Type *ty, unsigned vty, Use *OpList, unsigned NumOps)
|
IR: Move NumOperands from User to Value, NFC
Store `User::NumOperands` (and `MDNode::NumOperands`) in `Value`.
On 64-bit host architectures, this reduces `sizeof(User)` and all
subclasses by 8, and has no effect on `sizeof(Value)` (or, incidentally,
on `sizeof(MDNode)`).
On 32-bit host architectures, this increases `sizeof(Value)` by 4.
However, it has no effect on `sizeof(User)` and `sizeof(MDNode)`, so the
only concrete subclasses of `Value` that actually see the increase are
`BasicBlock`, `Argument`, `InlineAsm`, and `MDString`. Moreover, I'll
be shocked and confused if this causes a tangible memory regression.
This has no functionality change (other than memory footprint).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@219845 91177308-0d34-0410-b5e6-96231b3b80d8
2014-10-15 20:39:05 +00:00
|
|
|
: Value(ty, vty), OperandList(OpList) {
|
|
|
|
NumOperands = NumOps;
|
|
|
|
}
|
2008-05-10 08:32:32 +00:00
|
|
|
Use *allocHungoffUses(unsigned) const;
|
2011-01-16 15:30:52 +00:00
|
|
|
void dropHungoffUses() {
|
|
|
|
Use::zap(OperandList, OperandList + NumOperands, true);
|
2014-04-09 06:08:46 +00:00
|
|
|
OperandList = nullptr;
|
2011-01-26 21:56:10 +00:00
|
|
|
// Reset NumOperands so User::operator delete() does the right thing.
|
2011-01-16 15:30:52 +00:00
|
|
|
NumOperands = 0;
|
2008-05-10 08:32:32 +00:00
|
|
|
}
|
2008-04-06 20:25:17 +00:00
|
|
|
public:
|
2008-05-10 08:32:32 +00:00
|
|
|
~User() {
|
2011-01-07 20:29:02 +00:00
|
|
|
Use::zap(OperandList, OperandList + NumOperands);
|
2008-05-10 08:32:32 +00:00
|
|
|
}
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief Free memory allocated for User and Use objects.
|
2008-05-15 01:23:11 +00:00
|
|
|
void operator delete(void *Usr);
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief Placement delete - required by std, but never called.
|
2008-05-22 13:16:42 +00:00
|
|
|
void operator delete(void*, unsigned) {
|
2012-02-05 22:14:15 +00:00
|
|
|
llvm_unreachable("Constructor throws?");
|
2008-05-22 13:16:42 +00:00
|
|
|
}
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief Placement delete - required by std, but never called.
|
2009-03-19 23:26:52 +00:00
|
|
|
void operator delete(void*, unsigned, bool) {
|
2012-02-05 22:14:15 +00:00
|
|
|
llvm_unreachable("Constructor throws?");
|
2009-03-19 23:26:52 +00:00
|
|
|
}
|
2009-03-09 19:57:49 +00:00
|
|
|
protected:
|
2009-03-10 23:02:13 +00:00
|
|
|
template <int Idx, typename U> static Use &OpFrom(const U *that) {
|
|
|
|
return Idx < 0
|
|
|
|
? OperandTraits<U>::op_end(const_cast<U*>(that))[Idx]
|
|
|
|
: OperandTraits<U>::op_begin(const_cast<U*>(that))[Idx];
|
2008-05-10 08:32:32 +00:00
|
|
|
}
|
2009-03-10 23:02:13 +00:00
|
|
|
template <int Idx> Use &Op() {
|
|
|
|
return OpFrom<Idx>(this);
|
|
|
|
}
|
|
|
|
template <int Idx> const Use &Op() const {
|
|
|
|
return OpFrom<Idx>(this);
|
2008-05-10 08:32:32 +00:00
|
|
|
}
|
2009-03-09 19:57:49 +00:00
|
|
|
public:
|
2005-04-21 20:19:05 +00:00
|
|
|
Value *getOperand(unsigned i) const {
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
assert(i < NumOperands && "getOperand() out of range!");
|
|
|
|
return OperandList[i];
|
2001-07-07 08:36:50 +00:00
|
|
|
}
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
void setOperand(unsigned i, Value *Val) {
|
|
|
|
assert(i < NumOperands && "setOperand() out of range!");
|
2008-10-28 17:22:40 +00:00
|
|
|
assert((!isa<Constant>((const Value*)this) ||
|
|
|
|
isa<GlobalValue>((const Value*)this)) &&
|
|
|
|
"Cannot mutate a constant with setOperand!");
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
OperandList[i] = Val;
|
2001-07-07 08:36:50 +00:00
|
|
|
}
|
2009-01-31 07:34:19 +00:00
|
|
|
const Use &getOperandUse(unsigned i) const {
|
2011-03-21 16:38:22 +00:00
|
|
|
assert(i < NumOperands && "getOperandUse() out of range!");
|
2009-01-31 07:34:19 +00:00
|
|
|
return OperandList[i];
|
|
|
|
}
|
|
|
|
Use &getOperandUse(unsigned i) {
|
2011-03-21 16:38:22 +00:00
|
|
|
assert(i < NumOperands && "getOperandUse() out of range!");
|
2009-01-31 07:34:19 +00:00
|
|
|
return OperandList[i];
|
|
|
|
}
|
2012-10-09 16:55:14 +00:00
|
|
|
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
unsigned getNumOperands() const { return NumOperands; }
|
2001-07-07 08:36:50 +00:00
|
|
|
|
|
|
|
// ---------------------------------------------------------------------------
|
|
|
|
// Operand Iterator interface...
|
2001-06-06 20:29:01 +00:00
|
|
|
//
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
typedef Use* op_iterator;
|
|
|
|
typedef const Use* const_op_iterator;
|
2014-03-03 10:42:58 +00:00
|
|
|
typedef iterator_range<op_iterator> op_range;
|
|
|
|
typedef iterator_range<const_op_iterator> const_op_range;
|
2001-07-07 08:36:50 +00:00
|
|
|
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
inline op_iterator op_begin() { return OperandList; }
|
|
|
|
inline const_op_iterator op_begin() const { return OperandList; }
|
|
|
|
inline op_iterator op_end() { return OperandList+NumOperands; }
|
|
|
|
inline const_op_iterator op_end() const { return OperandList+NumOperands; }
|
2014-03-03 10:42:58 +00:00
|
|
|
inline op_range operands() {
|
2014-03-03 10:59:41 +00:00
|
|
|
return op_range(op_begin(), op_end());
|
2014-03-03 10:42:58 +00:00
|
|
|
}
|
|
|
|
inline const_op_range operands() const {
|
2014-03-03 10:59:41 +00:00
|
|
|
return const_op_range(op_begin(), op_end());
|
2014-03-03 10:42:58 +00:00
|
|
|
}
|
2003-06-17 22:15:55 +00:00
|
|
|
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief Iterator for directly iterating over the operand Values.
|
2014-04-24 05:33:53 +00:00
|
|
|
struct value_op_iterator
|
2014-04-29 01:57:35 +00:00
|
|
|
: iterator_adaptor_base<value_op_iterator, op_iterator,
|
|
|
|
std::random_access_iterator_tag, Value *,
|
|
|
|
ptrdiff_t, Value *, Value *> {
|
2014-04-24 05:33:53 +00:00
|
|
|
explicit value_op_iterator(Use *U = nullptr) : iterator_adaptor_base(U) {}
|
2012-10-09 16:55:14 +00:00
|
|
|
|
2014-04-24 05:33:53 +00:00
|
|
|
Value *operator*() const { return *I; }
|
2012-10-09 16:55:14 +00:00
|
|
|
Value *operator->() const { return operator*(); }
|
|
|
|
};
|
|
|
|
|
|
|
|
inline value_op_iterator value_op_begin() {
|
|
|
|
return value_op_iterator(op_begin());
|
|
|
|
}
|
|
|
|
inline value_op_iterator value_op_end() {
|
|
|
|
return value_op_iterator(op_end());
|
|
|
|
}
|
2014-03-03 10:42:58 +00:00
|
|
|
inline iterator_range<value_op_iterator> operand_values() {
|
2014-03-03 10:59:41 +00:00
|
|
|
return iterator_range<value_op_iterator>(value_op_begin(), value_op_end());
|
2014-03-03 10:42:58 +00:00
|
|
|
}
|
2012-10-09 16:55:14 +00:00
|
|
|
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief Drop all references to operands.
|
|
|
|
///
|
|
|
|
/// This function is in charge of "letting go" of all objects that this User
|
|
|
|
/// refers to. This allows one to 'delete' a whole class at a time, even
|
|
|
|
/// though there may be circular references... First all references are
|
|
|
|
/// dropped, and all use counts go to zero. Then everything is deleted for
|
|
|
|
/// real. Note that no operations are valid on an object that has "dropped
|
|
|
|
/// all references", except operator delete.
|
Instead of storing operands as std::vector<Use>, just maintain a pointer
and num operands in the User class. this allows us to embed the operands
directly in the subclasses if possible. For example, for binary operators
we store the two operands in the derived class.
The has several effects:
1. it improves locality because the operands and instruction are together
2. it makes accesses to operands faster (one less load) if you access them
through the derived class pointer. For example this:
Value *GetBinaryOperatorOp(BinaryOperator *I, int i) {
return I->getOperand(i);
}
Was compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 4(%esp), %edx
movl 8(%esp), %eax
sall $4, %eax
movl 24(%edx), %ecx
addl %ecx, %eax
movl (%eax), %eax
ret
and is now compiled to:
_Z19GetBinaryOperatorOpPN4llvm14BinaryOperatorEi:
movl 8(%esp), %eax
movl 4(%esp), %edx
sall $4, %eax
addl %edx, %eax
movl 44(%eax), %eax
ret
Accesses through "Instruction*" are unmodified.
3. This reduces memory consumption (by about 3%) by eliminating 1 word of
vector overhead and a malloc header on a seperate object.
4. This speeds up gccas about 10% (both debug and release builds) on
large things (such as 176.gcc). For example, it takes a debug build
from 172.9 -> 155.6s and a release gccas from 67.7 -> 61.8s
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@19883 91177308-0d34-0410-b5e6-96231b3b80d8
2005-01-29 00:29:39 +00:00
|
|
|
void dropAllReferences() {
|
2014-03-10 15:03:06 +00:00
|
|
|
for (Use &U : operands())
|
2014-04-09 06:08:46 +00:00
|
|
|
U.set(nullptr);
|
2001-07-07 08:36:50 +00:00
|
|
|
}
|
2001-06-06 20:29:01 +00:00
|
|
|
|
2014-10-15 20:28:31 +00:00
|
|
|
/// \brief Replace uses of one Value with another.
|
2002-08-25 22:54:55 +00:00
|
|
|
///
|
2014-10-15 20:28:31 +00:00
|
|
|
/// Replaces all references to the "From" definition with references to the
|
|
|
|
/// "To" definition.
|
2001-06-06 20:29:01 +00:00
|
|
|
void replaceUsesOfWith(Value *From, Value *To);
|
2001-07-08 18:38:18 +00:00
|
|
|
|
2001-10-13 06:18:05 +00:00
|
|
|
// Methods for support type inquiry through isa, cast, and dyn_cast:
|
|
|
|
static inline bool classof(const Value *V) {
|
2004-07-17 23:32:11 +00:00
|
|
|
return isa<Instruction>(V) || isa<Constant>(V);
|
2001-10-13 06:18:05 +00:00
|
|
|
}
|
2001-06-06 20:29:01 +00:00
|
|
|
};
|
|
|
|
|
2003-05-29 15:08:33 +00:00
|
|
|
template<> struct simplify_type<User::op_iterator> {
|
|
|
|
typedef Value* SimpleType;
|
2013-03-27 16:43:11 +00:00
|
|
|
static SimpleType getSimplifiedValue(User::op_iterator &Val) {
|
|
|
|
return Val->get();
|
2003-05-29 15:08:33 +00:00
|
|
|
}
|
|
|
|
};
|
|
|
|
template<> struct simplify_type<User::const_op_iterator> {
|
2013-03-27 16:43:11 +00:00
|
|
|
typedef /*const*/ Value* SimpleType;
|
|
|
|
static SimpleType getSimplifiedValue(User::const_op_iterator &Val) {
|
|
|
|
return Val->get();
|
2003-05-29 15:08:33 +00:00
|
|
|
}
|
|
|
|
};
|
2005-02-27 06:15:51 +00:00
|
|
|
|
2003-11-11 22:41:34 +00:00
|
|
|
} // End llvm namespace
|
|
|
|
|
2001-06-06 20:29:01 +00:00
|
|
|
#endif
|