2007-04-22 14:24:45 +08:00
|
|
|
//===-- Bitcode/Writer/ValueEnumerator.h - Number values --------*- C++ -*-===//
|
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
2007-12-30 04:36:04 +08:00
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
2007-04-22 14:24:45 +08:00
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// This class gives values and types Unique ID's.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
2014-08-14 00:26:38 +08:00
|
|
|
#ifndef LLVM_LIB_BITCODE_WRITER_VALUEENUMERATOR_H
|
|
|
|
#define LLVM_LIB_BITCODE_WRITER_VALUEENUMERATOR_H
|
2007-04-22 14:24:45 +08:00
|
|
|
|
|
|
|
#include "llvm/ADT/DenseMap.h"
|
2010-06-03 07:05:04 +08:00
|
|
|
#include "llvm/ADT/SmallVector.h"
|
2014-06-28 02:19:56 +08:00
|
|
|
#include "llvm/ADT/UniqueVector.h"
|
2013-01-02 19:36:10 +08:00
|
|
|
#include "llvm/IR/Attributes.h"
|
2014-07-29 05:19:41 +08:00
|
|
|
#include "llvm/IR/UseListOrder.h"
|
2007-04-22 14:24:45 +08:00
|
|
|
#include <vector>
|
|
|
|
|
|
|
|
namespace llvm {
|
|
|
|
|
|
|
|
class Type;
|
2007-04-26 12:42:16 +08:00
|
|
|
class Value;
|
2009-09-19 03:26:43 +08:00
|
|
|
class Instruction;
|
2007-04-26 12:42:16 +08:00
|
|
|
class BasicBlock;
|
2014-06-28 02:19:56 +08:00
|
|
|
class Comdat;
|
2007-04-22 14:24:45 +08:00
|
|
|
class Function;
|
2007-04-26 12:42:16 +08:00
|
|
|
class Module;
|
IR: Split Metadata from Value
Split `Metadata` away from the `Value` class hierarchy, as part of
PR21532. Assembly and bitcode changes are in the wings, but this is the
bulk of the change for the IR C++ API.
I have a follow-up patch prepared for `clang`. If this breaks other
sub-projects, I apologize in advance :(. Help me compile it on Darwin
I'll try to fix it. FWIW, the errors should be easy to fix, so it may
be simpler to just fix it yourself.
This breaks the build for all metadata-related code that's out-of-tree.
Rest assured the transition is mechanical and the compiler should catch
almost all of the problems.
Here's a quick guide for updating your code:
- `Metadata` is the root of a class hierarchy with three main classes:
`MDNode`, `MDString`, and `ValueAsMetadata`. It is distinct from
the `Value` class hierarchy. It is typeless -- i.e., instances do
*not* have a `Type`.
- `MDNode`'s operands are all `Metadata *` (instead of `Value *`).
- `TrackingVH<MDNode>` and `WeakVH` referring to metadata can be
replaced with `TrackingMDNodeRef` and `TrackingMDRef`, respectively.
If you're referring solely to resolved `MDNode`s -- post graph
construction -- just use `MDNode*`.
- `MDNode` (and the rest of `Metadata`) have only limited support for
`replaceAllUsesWith()`.
As long as an `MDNode` is pointing at a forward declaration -- the
result of `MDNode::getTemporary()` -- it maintains a side map of its
uses and can RAUW itself. Once the forward declarations are fully
resolved RAUW support is dropped on the ground. This means that
uniquing collisions on changing operands cause nodes to become
"distinct". (This already happened fairly commonly, whenever an
operand went to null.)
If you're constructing complex (non self-reference) `MDNode` cycles,
you need to call `MDNode::resolveCycles()` on each node (or on a
top-level node that somehow references all of the nodes). Also,
don't do that. Metadata cycles (and the RAUW machinery needed to
construct them) are expensive.
- An `MDNode` can only refer to a `Constant` through a bridge called
`ConstantAsMetadata` (one of the subclasses of `ValueAsMetadata`).
As a side effect, accessing an operand of an `MDNode` that is known
to be, e.g., `ConstantInt`, takes three steps: first, cast from
`Metadata` to `ConstantAsMetadata`; second, extract the `Constant`;
third, cast down to `ConstantInt`.
The eventual goal is to introduce `MDInt`/`MDFloat`/etc. and have
metadata schema owners transition away from using `Constant`s when
the type isn't important (and they don't care about referring to
`GlobalValue`s).
In the meantime, I've added transitional API to the `mdconst`
namespace that matches semantics with the old code, in order to
avoid adding the error-prone three-step equivalent to every call
site. If your old code was:
MDNode *N = foo();
bar(isa <ConstantInt>(N->getOperand(0)));
baz(cast <ConstantInt>(N->getOperand(1)));
bak(cast_or_null <ConstantInt>(N->getOperand(2)));
bat(dyn_cast <ConstantInt>(N->getOperand(3)));
bay(dyn_cast_or_null<ConstantInt>(N->getOperand(4)));
you can trivially match its semantics with:
MDNode *N = foo();
bar(mdconst::hasa <ConstantInt>(N->getOperand(0)));
baz(mdconst::extract <ConstantInt>(N->getOperand(1)));
bak(mdconst::extract_or_null <ConstantInt>(N->getOperand(2)));
bat(mdconst::dyn_extract <ConstantInt>(N->getOperand(3)));
bay(mdconst::dyn_extract_or_null<ConstantInt>(N->getOperand(4)));
and when you transition your metadata schema to `MDInt`:
MDNode *N = foo();
bar(isa <MDInt>(N->getOperand(0)));
baz(cast <MDInt>(N->getOperand(1)));
bak(cast_or_null <MDInt>(N->getOperand(2)));
bat(dyn_cast <MDInt>(N->getOperand(3)));
bay(dyn_cast_or_null<MDInt>(N->getOperand(4)));
- A `CallInst` -- specifically, intrinsic instructions -- can refer to
metadata through a bridge called `MetadataAsValue`. This is a
subclass of `Value` where `getType()->isMetadataTy()`.
`MetadataAsValue` is the *only* class that can legally refer to a
`LocalAsMetadata`, which is a bridged form of non-`Constant` values
like `Argument` and `Instruction`. It can also refer to any other
`Metadata` subclass.
(I'll break all your testcases in a follow-up commit, when I propagate
this change to assembly.)
llvm-svn: 223802
2014-12-10 02:38:53 +08:00
|
|
|
class Metadata;
|
|
|
|
class LocalAsMetadata;
|
2010-06-03 07:05:04 +08:00
|
|
|
class MDNode;
|
2010-01-09 08:30:14 +08:00
|
|
|
class NamedMDNode;
|
2012-12-08 07:16:57 +08:00
|
|
|
class AttributeSet;
|
2007-04-22 14:24:45 +08:00
|
|
|
class ValueSymbolTable;
|
2010-01-08 03:39:36 +08:00
|
|
|
class MDSymbolTable;
|
2011-12-08 04:44:46 +08:00
|
|
|
class raw_ostream;
|
2007-04-22 14:24:45 +08:00
|
|
|
|
2013-09-12 02:05:11 +08:00
|
|
|
class ValueEnumerator {
|
2007-04-22 14:24:45 +08:00
|
|
|
public:
|
2011-07-18 12:54:35 +08:00
|
|
|
typedef std::vector<Type*> TypeList;
|
2007-04-22 14:24:45 +08:00
|
|
|
|
|
|
|
// For each value, we remember its Value* and occurrence frequency.
|
|
|
|
typedef std::vector<std::pair<const Value*, unsigned> > ValueList;
|
2014-07-29 05:19:41 +08:00
|
|
|
|
|
|
|
UseListOrderStack UseListOrders;
|
|
|
|
|
2007-04-22 14:24:45 +08:00
|
|
|
private:
|
2011-07-18 12:54:35 +08:00
|
|
|
typedef DenseMap<Type*, unsigned> TypeMapType;
|
2007-04-22 14:24:45 +08:00
|
|
|
TypeMapType TypeMap;
|
2007-04-24 08:16:04 +08:00
|
|
|
TypeList Types;
|
2007-04-22 14:24:45 +08:00
|
|
|
|
|
|
|
typedef DenseMap<const Value*, unsigned> ValueMapType;
|
|
|
|
ValueMapType ValueMap;
|
2007-04-24 08:16:04 +08:00
|
|
|
ValueList Values;
|
2014-06-28 02:19:56 +08:00
|
|
|
|
|
|
|
typedef UniqueVector<const Comdat *> ComdatSetType;
|
|
|
|
ComdatSetType Comdats;
|
|
|
|
|
IR: Split Metadata from Value
Split `Metadata` away from the `Value` class hierarchy, as part of
PR21532. Assembly and bitcode changes are in the wings, but this is the
bulk of the change for the IR C++ API.
I have a follow-up patch prepared for `clang`. If this breaks other
sub-projects, I apologize in advance :(. Help me compile it on Darwin
I'll try to fix it. FWIW, the errors should be easy to fix, so it may
be simpler to just fix it yourself.
This breaks the build for all metadata-related code that's out-of-tree.
Rest assured the transition is mechanical and the compiler should catch
almost all of the problems.
Here's a quick guide for updating your code:
- `Metadata` is the root of a class hierarchy with three main classes:
`MDNode`, `MDString`, and `ValueAsMetadata`. It is distinct from
the `Value` class hierarchy. It is typeless -- i.e., instances do
*not* have a `Type`.
- `MDNode`'s operands are all `Metadata *` (instead of `Value *`).
- `TrackingVH<MDNode>` and `WeakVH` referring to metadata can be
replaced with `TrackingMDNodeRef` and `TrackingMDRef`, respectively.
If you're referring solely to resolved `MDNode`s -- post graph
construction -- just use `MDNode*`.
- `MDNode` (and the rest of `Metadata`) have only limited support for
`replaceAllUsesWith()`.
As long as an `MDNode` is pointing at a forward declaration -- the
result of `MDNode::getTemporary()` -- it maintains a side map of its
uses and can RAUW itself. Once the forward declarations are fully
resolved RAUW support is dropped on the ground. This means that
uniquing collisions on changing operands cause nodes to become
"distinct". (This already happened fairly commonly, whenever an
operand went to null.)
If you're constructing complex (non self-reference) `MDNode` cycles,
you need to call `MDNode::resolveCycles()` on each node (or on a
top-level node that somehow references all of the nodes). Also,
don't do that. Metadata cycles (and the RAUW machinery needed to
construct them) are expensive.
- An `MDNode` can only refer to a `Constant` through a bridge called
`ConstantAsMetadata` (one of the subclasses of `ValueAsMetadata`).
As a side effect, accessing an operand of an `MDNode` that is known
to be, e.g., `ConstantInt`, takes three steps: first, cast from
`Metadata` to `ConstantAsMetadata`; second, extract the `Constant`;
third, cast down to `ConstantInt`.
The eventual goal is to introduce `MDInt`/`MDFloat`/etc. and have
metadata schema owners transition away from using `Constant`s when
the type isn't important (and they don't care about referring to
`GlobalValue`s).
In the meantime, I've added transitional API to the `mdconst`
namespace that matches semantics with the old code, in order to
avoid adding the error-prone three-step equivalent to every call
site. If your old code was:
MDNode *N = foo();
bar(isa <ConstantInt>(N->getOperand(0)));
baz(cast <ConstantInt>(N->getOperand(1)));
bak(cast_or_null <ConstantInt>(N->getOperand(2)));
bat(dyn_cast <ConstantInt>(N->getOperand(3)));
bay(dyn_cast_or_null<ConstantInt>(N->getOperand(4)));
you can trivially match its semantics with:
MDNode *N = foo();
bar(mdconst::hasa <ConstantInt>(N->getOperand(0)));
baz(mdconst::extract <ConstantInt>(N->getOperand(1)));
bak(mdconst::extract_or_null <ConstantInt>(N->getOperand(2)));
bat(mdconst::dyn_extract <ConstantInt>(N->getOperand(3)));
bay(mdconst::dyn_extract_or_null<ConstantInt>(N->getOperand(4)));
and when you transition your metadata schema to `MDInt`:
MDNode *N = foo();
bar(isa <MDInt>(N->getOperand(0)));
baz(cast <MDInt>(N->getOperand(1)));
bak(cast_or_null <MDInt>(N->getOperand(2)));
bat(dyn_cast <MDInt>(N->getOperand(3)));
bay(dyn_cast_or_null<MDInt>(N->getOperand(4)));
- A `CallInst` -- specifically, intrinsic instructions -- can refer to
metadata through a bridge called `MetadataAsValue`. This is a
subclass of `Value` where `getType()->isMetadataTy()`.
`MetadataAsValue` is the *only* class that can legally refer to a
`LocalAsMetadata`, which is a bridged form of non-`Constant` values
like `Argument` and `Instruction`. It can also refer to any other
`Metadata` subclass.
(I'll break all your testcases in a follow-up commit, when I propagate
this change to assembly.)
llvm-svn: 223802
2014-12-10 02:38:53 +08:00
|
|
|
std::vector<const Metadata *> MDs;
|
|
|
|
SmallVector<const LocalAsMetadata *, 8> FunctionLocalMDs;
|
|
|
|
typedef DenseMap<const Metadata *, unsigned> MetadataMapType;
|
|
|
|
MetadataMapType MDValueMap;
|
2015-01-13 06:30:34 +08:00
|
|
|
bool HasMDString;
|
2015-04-30 00:38:44 +08:00
|
|
|
bool HasDILocation;
|
|
|
|
bool HasGenericDINode;
|
2015-04-15 07:45:11 +08:00
|
|
|
bool ShouldPreserveUseListOrder;
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2013-02-12 06:33:26 +08:00
|
|
|
typedef DenseMap<AttributeSet, unsigned> AttributeGroupMapType;
|
|
|
|
AttributeGroupMapType AttributeGroupMap;
|
|
|
|
std::vector<AttributeSet> AttributeGroups;
|
2013-02-11 07:06:02 +08:00
|
|
|
|
2013-02-12 16:01:22 +08:00
|
|
|
typedef DenseMap<AttributeSet, unsigned> AttributeMapType;
|
2008-09-26 05:00:45 +08:00
|
|
|
AttributeMapType AttributeMap;
|
2012-12-19 15:18:57 +08:00
|
|
|
std::vector<AttributeSet> Attribute;
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2009-10-28 13:24:40 +08:00
|
|
|
/// GlobalBasicBlockIDs - This map memoizes the basic block ID's referenced by
|
|
|
|
/// the "getGlobalBasicBlockID" method.
|
|
|
|
mutable DenseMap<const BasicBlock*, unsigned> GlobalBasicBlockIDs;
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2009-09-19 03:26:43 +08:00
|
|
|
typedef DenseMap<const Instruction*, unsigned> InstructionMapType;
|
|
|
|
InstructionMapType InstructionMap;
|
|
|
|
unsigned InstructionCount;
|
|
|
|
|
2007-04-26 12:42:16 +08:00
|
|
|
/// BasicBlocks - This contains all the basic blocks for the currently
|
|
|
|
/// incorporated function. Their reverse mapping is stored in ValueMap.
|
|
|
|
std::vector<const BasicBlock*> BasicBlocks;
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2007-04-26 11:50:57 +08:00
|
|
|
/// When a function is incorporated, this is the size of the Values list
|
|
|
|
/// before incorporation.
|
2007-04-26 13:53:54 +08:00
|
|
|
unsigned NumModuleValues;
|
2010-08-24 10:24:03 +08:00
|
|
|
|
|
|
|
/// When a function is incorporated, this is the size of the MDValues list
|
|
|
|
/// before incorporation.
|
IR: Split Metadata from Value
Split `Metadata` away from the `Value` class hierarchy, as part of
PR21532. Assembly and bitcode changes are in the wings, but this is the
bulk of the change for the IR C++ API.
I have a follow-up patch prepared for `clang`. If this breaks other
sub-projects, I apologize in advance :(. Help me compile it on Darwin
I'll try to fix it. FWIW, the errors should be easy to fix, so it may
be simpler to just fix it yourself.
This breaks the build for all metadata-related code that's out-of-tree.
Rest assured the transition is mechanical and the compiler should catch
almost all of the problems.
Here's a quick guide for updating your code:
- `Metadata` is the root of a class hierarchy with three main classes:
`MDNode`, `MDString`, and `ValueAsMetadata`. It is distinct from
the `Value` class hierarchy. It is typeless -- i.e., instances do
*not* have a `Type`.
- `MDNode`'s operands are all `Metadata *` (instead of `Value *`).
- `TrackingVH<MDNode>` and `WeakVH` referring to metadata can be
replaced with `TrackingMDNodeRef` and `TrackingMDRef`, respectively.
If you're referring solely to resolved `MDNode`s -- post graph
construction -- just use `MDNode*`.
- `MDNode` (and the rest of `Metadata`) have only limited support for
`replaceAllUsesWith()`.
As long as an `MDNode` is pointing at a forward declaration -- the
result of `MDNode::getTemporary()` -- it maintains a side map of its
uses and can RAUW itself. Once the forward declarations are fully
resolved RAUW support is dropped on the ground. This means that
uniquing collisions on changing operands cause nodes to become
"distinct". (This already happened fairly commonly, whenever an
operand went to null.)
If you're constructing complex (non self-reference) `MDNode` cycles,
you need to call `MDNode::resolveCycles()` on each node (or on a
top-level node that somehow references all of the nodes). Also,
don't do that. Metadata cycles (and the RAUW machinery needed to
construct them) are expensive.
- An `MDNode` can only refer to a `Constant` through a bridge called
`ConstantAsMetadata` (one of the subclasses of `ValueAsMetadata`).
As a side effect, accessing an operand of an `MDNode` that is known
to be, e.g., `ConstantInt`, takes three steps: first, cast from
`Metadata` to `ConstantAsMetadata`; second, extract the `Constant`;
third, cast down to `ConstantInt`.
The eventual goal is to introduce `MDInt`/`MDFloat`/etc. and have
metadata schema owners transition away from using `Constant`s when
the type isn't important (and they don't care about referring to
`GlobalValue`s).
In the meantime, I've added transitional API to the `mdconst`
namespace that matches semantics with the old code, in order to
avoid adding the error-prone three-step equivalent to every call
site. If your old code was:
MDNode *N = foo();
bar(isa <ConstantInt>(N->getOperand(0)));
baz(cast <ConstantInt>(N->getOperand(1)));
bak(cast_or_null <ConstantInt>(N->getOperand(2)));
bat(dyn_cast <ConstantInt>(N->getOperand(3)));
bay(dyn_cast_or_null<ConstantInt>(N->getOperand(4)));
you can trivially match its semantics with:
MDNode *N = foo();
bar(mdconst::hasa <ConstantInt>(N->getOperand(0)));
baz(mdconst::extract <ConstantInt>(N->getOperand(1)));
bak(mdconst::extract_or_null <ConstantInt>(N->getOperand(2)));
bat(mdconst::dyn_extract <ConstantInt>(N->getOperand(3)));
bay(mdconst::dyn_extract_or_null<ConstantInt>(N->getOperand(4)));
and when you transition your metadata schema to `MDInt`:
MDNode *N = foo();
bar(isa <MDInt>(N->getOperand(0)));
baz(cast <MDInt>(N->getOperand(1)));
bak(cast_or_null <MDInt>(N->getOperand(2)));
bat(dyn_cast <MDInt>(N->getOperand(3)));
bay(dyn_cast_or_null<MDInt>(N->getOperand(4)));
- A `CallInst` -- specifically, intrinsic instructions -- can refer to
metadata through a bridge called `MetadataAsValue`. This is a
subclass of `Value` where `getType()->isMetadataTy()`.
`MetadataAsValue` is the *only* class that can legally refer to a
`LocalAsMetadata`, which is a bridged form of non-`Constant` values
like `Argument` and `Instruction`. It can also refer to any other
`Metadata` subclass.
(I'll break all your testcases in a follow-up commit, when I propagate
this change to assembly.)
llvm-svn: 223802
2014-12-10 02:38:53 +08:00
|
|
|
unsigned NumModuleMDs;
|
2010-08-24 10:24:03 +08:00
|
|
|
|
2007-04-26 13:53:54 +08:00
|
|
|
unsigned FirstFuncConstantID;
|
|
|
|
unsigned FirstInstID;
|
2012-09-16 01:09:36 +08:00
|
|
|
|
2015-02-16 06:54:22 +08:00
|
|
|
ValueEnumerator(const ValueEnumerator &) = delete;
|
|
|
|
void operator=(const ValueEnumerator &) = delete;
|
2007-04-22 14:24:45 +08:00
|
|
|
public:
|
2015-04-15 07:45:11 +08:00
|
|
|
ValueEnumerator(const Module &M, bool ShouldPreserveUseListOrder);
|
2007-04-22 14:24:45 +08:00
|
|
|
|
2011-12-08 04:44:46 +08:00
|
|
|
void dump() const;
|
|
|
|
void print(raw_ostream &OS, const ValueMapType &Map, const char *Name) const;
|
IR: Split Metadata from Value
Split `Metadata` away from the `Value` class hierarchy, as part of
PR21532. Assembly and bitcode changes are in the wings, but this is the
bulk of the change for the IR C++ API.
I have a follow-up patch prepared for `clang`. If this breaks other
sub-projects, I apologize in advance :(. Help me compile it on Darwin
I'll try to fix it. FWIW, the errors should be easy to fix, so it may
be simpler to just fix it yourself.
This breaks the build for all metadata-related code that's out-of-tree.
Rest assured the transition is mechanical and the compiler should catch
almost all of the problems.
Here's a quick guide for updating your code:
- `Metadata` is the root of a class hierarchy with three main classes:
`MDNode`, `MDString`, and `ValueAsMetadata`. It is distinct from
the `Value` class hierarchy. It is typeless -- i.e., instances do
*not* have a `Type`.
- `MDNode`'s operands are all `Metadata *` (instead of `Value *`).
- `TrackingVH<MDNode>` and `WeakVH` referring to metadata can be
replaced with `TrackingMDNodeRef` and `TrackingMDRef`, respectively.
If you're referring solely to resolved `MDNode`s -- post graph
construction -- just use `MDNode*`.
- `MDNode` (and the rest of `Metadata`) have only limited support for
`replaceAllUsesWith()`.
As long as an `MDNode` is pointing at a forward declaration -- the
result of `MDNode::getTemporary()` -- it maintains a side map of its
uses and can RAUW itself. Once the forward declarations are fully
resolved RAUW support is dropped on the ground. This means that
uniquing collisions on changing operands cause nodes to become
"distinct". (This already happened fairly commonly, whenever an
operand went to null.)
If you're constructing complex (non self-reference) `MDNode` cycles,
you need to call `MDNode::resolveCycles()` on each node (or on a
top-level node that somehow references all of the nodes). Also,
don't do that. Metadata cycles (and the RAUW machinery needed to
construct them) are expensive.
- An `MDNode` can only refer to a `Constant` through a bridge called
`ConstantAsMetadata` (one of the subclasses of `ValueAsMetadata`).
As a side effect, accessing an operand of an `MDNode` that is known
to be, e.g., `ConstantInt`, takes three steps: first, cast from
`Metadata` to `ConstantAsMetadata`; second, extract the `Constant`;
third, cast down to `ConstantInt`.
The eventual goal is to introduce `MDInt`/`MDFloat`/etc. and have
metadata schema owners transition away from using `Constant`s when
the type isn't important (and they don't care about referring to
`GlobalValue`s).
In the meantime, I've added transitional API to the `mdconst`
namespace that matches semantics with the old code, in order to
avoid adding the error-prone three-step equivalent to every call
site. If your old code was:
MDNode *N = foo();
bar(isa <ConstantInt>(N->getOperand(0)));
baz(cast <ConstantInt>(N->getOperand(1)));
bak(cast_or_null <ConstantInt>(N->getOperand(2)));
bat(dyn_cast <ConstantInt>(N->getOperand(3)));
bay(dyn_cast_or_null<ConstantInt>(N->getOperand(4)));
you can trivially match its semantics with:
MDNode *N = foo();
bar(mdconst::hasa <ConstantInt>(N->getOperand(0)));
baz(mdconst::extract <ConstantInt>(N->getOperand(1)));
bak(mdconst::extract_or_null <ConstantInt>(N->getOperand(2)));
bat(mdconst::dyn_extract <ConstantInt>(N->getOperand(3)));
bay(mdconst::dyn_extract_or_null<ConstantInt>(N->getOperand(4)));
and when you transition your metadata schema to `MDInt`:
MDNode *N = foo();
bar(isa <MDInt>(N->getOperand(0)));
baz(cast <MDInt>(N->getOperand(1)));
bak(cast_or_null <MDInt>(N->getOperand(2)));
bat(dyn_cast <MDInt>(N->getOperand(3)));
bay(dyn_cast_or_null<MDInt>(N->getOperand(4)));
- A `CallInst` -- specifically, intrinsic instructions -- can refer to
metadata through a bridge called `MetadataAsValue`. This is a
subclass of `Value` where `getType()->isMetadataTy()`.
`MetadataAsValue` is the *only* class that can legally refer to a
`LocalAsMetadata`, which is a bridged form of non-`Constant` values
like `Argument` and `Instruction`. It can also refer to any other
`Metadata` subclass.
(I'll break all your testcases in a follow-up commit, when I propagate
this change to assembly.)
llvm-svn: 223802
2014-12-10 02:38:53 +08:00
|
|
|
void print(raw_ostream &OS, const MetadataMapType &Map,
|
|
|
|
const char *Name) const;
|
2011-12-08 04:44:46 +08:00
|
|
|
|
2009-08-04 14:00:18 +08:00
|
|
|
unsigned getValueID(const Value *V) const;
|
2015-01-20 09:00:23 +08:00
|
|
|
unsigned getMetadataID(const Metadata *MD) const {
|
|
|
|
auto ID = getMetadataOrNullID(MD);
|
|
|
|
assert(ID != 0 && "Metadata not in slotcalculator!");
|
|
|
|
return ID - 1;
|
|
|
|
}
|
|
|
|
unsigned getMetadataOrNullID(const Metadata *MD) const {
|
|
|
|
return MDValueMap.lookup(MD);
|
|
|
|
}
|
2009-08-04 14:00:18 +08:00
|
|
|
|
2015-01-13 06:30:34 +08:00
|
|
|
bool hasMDString() const { return HasMDString; }
|
2015-04-30 00:38:44 +08:00
|
|
|
bool hasDILocation() const { return HasDILocation; }
|
|
|
|
bool hasGenericDINode() const { return HasGenericDINode; }
|
2015-01-13 06:30:34 +08:00
|
|
|
|
2015-04-15 07:45:11 +08:00
|
|
|
bool shouldPreserveUseListOrder() const { return ShouldPreserveUseListOrder; }
|
|
|
|
|
2011-07-18 12:54:35 +08:00
|
|
|
unsigned getTypeID(Type *T) const {
|
2007-04-22 14:24:45 +08:00
|
|
|
TypeMapType::const_iterator I = TypeMap.find(T);
|
|
|
|
assert(I != TypeMap.end() && "Type not in ValueEnumerator!");
|
|
|
|
return I->second-1;
|
|
|
|
}
|
2009-09-19 03:26:43 +08:00
|
|
|
|
|
|
|
unsigned getInstructionID(const Instruction *I) const;
|
|
|
|
void setInstructionID(const Instruction *I);
|
|
|
|
|
2013-02-12 06:33:26 +08:00
|
|
|
unsigned getAttributeID(AttributeSet PAL) const {
|
2008-03-13 01:45:29 +08:00
|
|
|
if (PAL.isEmpty()) return 0; // Null maps to zero.
|
2013-02-12 16:01:22 +08:00
|
|
|
AttributeMapType::const_iterator I = AttributeMap.find(PAL);
|
2008-09-26 05:00:45 +08:00
|
|
|
assert(I != AttributeMap.end() && "Attribute not in ValueEnumerator!");
|
2007-05-04 06:46:43 +08:00
|
|
|
return I->second;
|
|
|
|
}
|
2007-04-22 14:24:45 +08:00
|
|
|
|
2013-02-12 06:33:26 +08:00
|
|
|
unsigned getAttributeGroupID(AttributeSet PAL) const {
|
2013-02-11 07:06:02 +08:00
|
|
|
if (PAL.isEmpty()) return 0; // Null maps to zero.
|
2013-02-12 06:33:26 +08:00
|
|
|
AttributeGroupMapType::const_iterator I = AttributeGroupMap.find(PAL);
|
|
|
|
assert(I != AttributeGroupMap.end() && "Attribute not in ValueEnumerator!");
|
2013-02-11 07:06:02 +08:00
|
|
|
return I->second;
|
|
|
|
}
|
|
|
|
|
2007-04-26 13:53:54 +08:00
|
|
|
/// getFunctionConstantRange - Return the range of values that corresponds to
|
|
|
|
/// function-local constants.
|
|
|
|
void getFunctionConstantRange(unsigned &Start, unsigned &End) const {
|
|
|
|
Start = FirstFuncConstantID;
|
|
|
|
End = FirstInstID;
|
|
|
|
}
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2007-04-24 08:16:04 +08:00
|
|
|
const ValueList &getValues() const { return Values; }
|
IR: Split Metadata from Value
Split `Metadata` away from the `Value` class hierarchy, as part of
PR21532. Assembly and bitcode changes are in the wings, but this is the
bulk of the change for the IR C++ API.
I have a follow-up patch prepared for `clang`. If this breaks other
sub-projects, I apologize in advance :(. Help me compile it on Darwin
I'll try to fix it. FWIW, the errors should be easy to fix, so it may
be simpler to just fix it yourself.
This breaks the build for all metadata-related code that's out-of-tree.
Rest assured the transition is mechanical and the compiler should catch
almost all of the problems.
Here's a quick guide for updating your code:
- `Metadata` is the root of a class hierarchy with three main classes:
`MDNode`, `MDString`, and `ValueAsMetadata`. It is distinct from
the `Value` class hierarchy. It is typeless -- i.e., instances do
*not* have a `Type`.
- `MDNode`'s operands are all `Metadata *` (instead of `Value *`).
- `TrackingVH<MDNode>` and `WeakVH` referring to metadata can be
replaced with `TrackingMDNodeRef` and `TrackingMDRef`, respectively.
If you're referring solely to resolved `MDNode`s -- post graph
construction -- just use `MDNode*`.
- `MDNode` (and the rest of `Metadata`) have only limited support for
`replaceAllUsesWith()`.
As long as an `MDNode` is pointing at a forward declaration -- the
result of `MDNode::getTemporary()` -- it maintains a side map of its
uses and can RAUW itself. Once the forward declarations are fully
resolved RAUW support is dropped on the ground. This means that
uniquing collisions on changing operands cause nodes to become
"distinct". (This already happened fairly commonly, whenever an
operand went to null.)
If you're constructing complex (non self-reference) `MDNode` cycles,
you need to call `MDNode::resolveCycles()` on each node (or on a
top-level node that somehow references all of the nodes). Also,
don't do that. Metadata cycles (and the RAUW machinery needed to
construct them) are expensive.
- An `MDNode` can only refer to a `Constant` through a bridge called
`ConstantAsMetadata` (one of the subclasses of `ValueAsMetadata`).
As a side effect, accessing an operand of an `MDNode` that is known
to be, e.g., `ConstantInt`, takes three steps: first, cast from
`Metadata` to `ConstantAsMetadata`; second, extract the `Constant`;
third, cast down to `ConstantInt`.
The eventual goal is to introduce `MDInt`/`MDFloat`/etc. and have
metadata schema owners transition away from using `Constant`s when
the type isn't important (and they don't care about referring to
`GlobalValue`s).
In the meantime, I've added transitional API to the `mdconst`
namespace that matches semantics with the old code, in order to
avoid adding the error-prone three-step equivalent to every call
site. If your old code was:
MDNode *N = foo();
bar(isa <ConstantInt>(N->getOperand(0)));
baz(cast <ConstantInt>(N->getOperand(1)));
bak(cast_or_null <ConstantInt>(N->getOperand(2)));
bat(dyn_cast <ConstantInt>(N->getOperand(3)));
bay(dyn_cast_or_null<ConstantInt>(N->getOperand(4)));
you can trivially match its semantics with:
MDNode *N = foo();
bar(mdconst::hasa <ConstantInt>(N->getOperand(0)));
baz(mdconst::extract <ConstantInt>(N->getOperand(1)));
bak(mdconst::extract_or_null <ConstantInt>(N->getOperand(2)));
bat(mdconst::dyn_extract <ConstantInt>(N->getOperand(3)));
bay(mdconst::dyn_extract_or_null<ConstantInt>(N->getOperand(4)));
and when you transition your metadata schema to `MDInt`:
MDNode *N = foo();
bar(isa <MDInt>(N->getOperand(0)));
baz(cast <MDInt>(N->getOperand(1)));
bak(cast_or_null <MDInt>(N->getOperand(2)));
bat(dyn_cast <MDInt>(N->getOperand(3)));
bay(dyn_cast_or_null<MDInt>(N->getOperand(4)));
- A `CallInst` -- specifically, intrinsic instructions -- can refer to
metadata through a bridge called `MetadataAsValue`. This is a
subclass of `Value` where `getType()->isMetadataTy()`.
`MetadataAsValue` is the *only* class that can legally refer to a
`LocalAsMetadata`, which is a bridged form of non-`Constant` values
like `Argument` and `Instruction`. It can also refer to any other
`Metadata` subclass.
(I'll break all your testcases in a follow-up commit, when I propagate
this change to assembly.)
llvm-svn: 223802
2014-12-10 02:38:53 +08:00
|
|
|
const std::vector<const Metadata *> &getMDs() const { return MDs; }
|
|
|
|
const SmallVectorImpl<const LocalAsMetadata *> &getFunctionLocalMDs() const {
|
2010-06-03 07:05:04 +08:00
|
|
|
return FunctionLocalMDs;
|
|
|
|
}
|
2007-04-22 14:24:45 +08:00
|
|
|
const TypeList &getTypes() const { return Types; }
|
2007-04-26 12:42:16 +08:00
|
|
|
const std::vector<const BasicBlock*> &getBasicBlocks() const {
|
2012-11-25 23:23:39 +08:00
|
|
|
return BasicBlocks;
|
2007-04-26 12:42:16 +08:00
|
|
|
}
|
2012-12-08 07:16:57 +08:00
|
|
|
const std::vector<AttributeSet> &getAttributes() const {
|
2012-12-19 15:18:57 +08:00
|
|
|
return Attribute;
|
2007-05-04 06:46:43 +08:00
|
|
|
}
|
2013-02-12 06:33:26 +08:00
|
|
|
const std::vector<AttributeSet> &getAttributeGroups() const {
|
|
|
|
return AttributeGroups;
|
2013-02-11 07:06:02 +08:00
|
|
|
}
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2014-06-28 02:19:56 +08:00
|
|
|
const ComdatSetType &getComdats() const { return Comdats; }
|
|
|
|
unsigned getComdatID(const Comdat *C) const;
|
|
|
|
|
2009-10-28 13:24:40 +08:00
|
|
|
/// getGlobalBasicBlockID - This returns the function-specific ID for the
|
|
|
|
/// specified basic block. This is relatively expensive information, so it
|
|
|
|
/// should only be used by rare constructs such as address-of-label.
|
|
|
|
unsigned getGlobalBasicBlockID(const BasicBlock *BB) const;
|
2007-04-22 14:24:45 +08:00
|
|
|
|
2011-06-04 01:02:19 +08:00
|
|
|
/// incorporateFunction/purgeFunction - If you'd like to deal with a function,
|
2007-04-22 14:24:45 +08:00
|
|
|
/// use these two methods to get its data into the ValueEnumerator!
|
|
|
|
///
|
2011-06-04 01:02:19 +08:00
|
|
|
void incorporateFunction(const Function &F);
|
|
|
|
void purgeFunction();
|
2015-02-25 08:51:52 +08:00
|
|
|
uint64_t computeBitsRequiredForTypeIndicies() const;
|
2007-04-22 14:24:45 +08:00
|
|
|
|
|
|
|
private:
|
2007-05-04 13:21:47 +08:00
|
|
|
void OptimizeConstants(unsigned CstStart, unsigned CstEnd);
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2010-08-24 10:24:03 +08:00
|
|
|
void EnumerateMDNodeOperands(const MDNode *N);
|
IR: Split Metadata from Value
Split `Metadata` away from the `Value` class hierarchy, as part of
PR21532. Assembly and bitcode changes are in the wings, but this is the
bulk of the change for the IR C++ API.
I have a follow-up patch prepared for `clang`. If this breaks other
sub-projects, I apologize in advance :(. Help me compile it on Darwin
I'll try to fix it. FWIW, the errors should be easy to fix, so it may
be simpler to just fix it yourself.
This breaks the build for all metadata-related code that's out-of-tree.
Rest assured the transition is mechanical and the compiler should catch
almost all of the problems.
Here's a quick guide for updating your code:
- `Metadata` is the root of a class hierarchy with three main classes:
`MDNode`, `MDString`, and `ValueAsMetadata`. It is distinct from
the `Value` class hierarchy. It is typeless -- i.e., instances do
*not* have a `Type`.
- `MDNode`'s operands are all `Metadata *` (instead of `Value *`).
- `TrackingVH<MDNode>` and `WeakVH` referring to metadata can be
replaced with `TrackingMDNodeRef` and `TrackingMDRef`, respectively.
If you're referring solely to resolved `MDNode`s -- post graph
construction -- just use `MDNode*`.
- `MDNode` (and the rest of `Metadata`) have only limited support for
`replaceAllUsesWith()`.
As long as an `MDNode` is pointing at a forward declaration -- the
result of `MDNode::getTemporary()` -- it maintains a side map of its
uses and can RAUW itself. Once the forward declarations are fully
resolved RAUW support is dropped on the ground. This means that
uniquing collisions on changing operands cause nodes to become
"distinct". (This already happened fairly commonly, whenever an
operand went to null.)
If you're constructing complex (non self-reference) `MDNode` cycles,
you need to call `MDNode::resolveCycles()` on each node (or on a
top-level node that somehow references all of the nodes). Also,
don't do that. Metadata cycles (and the RAUW machinery needed to
construct them) are expensive.
- An `MDNode` can only refer to a `Constant` through a bridge called
`ConstantAsMetadata` (one of the subclasses of `ValueAsMetadata`).
As a side effect, accessing an operand of an `MDNode` that is known
to be, e.g., `ConstantInt`, takes three steps: first, cast from
`Metadata` to `ConstantAsMetadata`; second, extract the `Constant`;
third, cast down to `ConstantInt`.
The eventual goal is to introduce `MDInt`/`MDFloat`/etc. and have
metadata schema owners transition away from using `Constant`s when
the type isn't important (and they don't care about referring to
`GlobalValue`s).
In the meantime, I've added transitional API to the `mdconst`
namespace that matches semantics with the old code, in order to
avoid adding the error-prone three-step equivalent to every call
site. If your old code was:
MDNode *N = foo();
bar(isa <ConstantInt>(N->getOperand(0)));
baz(cast <ConstantInt>(N->getOperand(1)));
bak(cast_or_null <ConstantInt>(N->getOperand(2)));
bat(dyn_cast <ConstantInt>(N->getOperand(3)));
bay(dyn_cast_or_null<ConstantInt>(N->getOperand(4)));
you can trivially match its semantics with:
MDNode *N = foo();
bar(mdconst::hasa <ConstantInt>(N->getOperand(0)));
baz(mdconst::extract <ConstantInt>(N->getOperand(1)));
bak(mdconst::extract_or_null <ConstantInt>(N->getOperand(2)));
bat(mdconst::dyn_extract <ConstantInt>(N->getOperand(3)));
bay(mdconst::dyn_extract_or_null<ConstantInt>(N->getOperand(4)));
and when you transition your metadata schema to `MDInt`:
MDNode *N = foo();
bar(isa <MDInt>(N->getOperand(0)));
baz(cast <MDInt>(N->getOperand(1)));
bak(cast_or_null <MDInt>(N->getOperand(2)));
bat(dyn_cast <MDInt>(N->getOperand(3)));
bay(dyn_cast_or_null<MDInt>(N->getOperand(4)));
- A `CallInst` -- specifically, intrinsic instructions -- can refer to
metadata through a bridge called `MetadataAsValue`. This is a
subclass of `Value` where `getType()->isMetadataTy()`.
`MetadataAsValue` is the *only* class that can legally refer to a
`LocalAsMetadata`, which is a bridged form of non-`Constant` values
like `Argument` and `Instruction`. It can also refer to any other
`Metadata` subclass.
(I'll break all your testcases in a follow-up commit, when I propagate
this change to assembly.)
llvm-svn: 223802
2014-12-10 02:38:53 +08:00
|
|
|
void EnumerateMetadata(const Metadata *MD);
|
|
|
|
void EnumerateFunctionLocalMetadata(const LocalAsMetadata *Local);
|
2010-01-09 08:30:14 +08:00
|
|
|
void EnumerateNamedMDNode(const NamedMDNode *NMD);
|
2010-01-15 03:54:11 +08:00
|
|
|
void EnumerateValue(const Value *V);
|
2011-07-18 12:54:35 +08:00
|
|
|
void EnumerateType(Type *T);
|
2010-01-15 03:54:11 +08:00
|
|
|
void EnumerateOperandType(const Value *V);
|
2013-02-12 16:01:22 +08:00
|
|
|
void EnumerateAttributes(AttributeSet PAL);
|
2012-11-25 23:23:39 +08:00
|
|
|
|
2007-04-22 14:24:45 +08:00
|
|
|
void EnumerateValueSymbolTable(const ValueSymbolTable &ST);
|
2014-11-18 04:06:27 +08:00
|
|
|
void EnumerateNamedMetadata(const Module &M);
|
2007-04-22 14:24:45 +08:00
|
|
|
};
|
|
|
|
|
2015-06-23 17:49:53 +08:00
|
|
|
} // End llvm namespace
|
2007-04-22 14:24:45 +08:00
|
|
|
|
|
|
|
#endif
|