2008-10-22 02:51:53 +00:00
|
|
|
add_llvm_library(LLVMCore
|
2008-09-22 01:08:49 +00:00
|
|
|
AsmWriter.cpp
|
2008-09-24 01:58:12 +00:00
|
|
|
Attributes.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
AutoUpgrade.cpp
|
|
|
|
BasicBlock.cpp
|
2014-06-27 18:19:56 +00:00
|
|
|
Comdat.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
ConstantFold.cpp
|
2014-03-04 12:24:34 +00:00
|
|
|
ConstantRange.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Constants.cpp
|
|
|
|
Core.cpp
|
2013-11-09 12:26:54 +00:00
|
|
|
DIBuilder.cpp
|
2012-10-04 22:08:14 +00:00
|
|
|
DataLayout.cpp
|
2012-06-28 00:18:12 +00:00
|
|
|
DebugInfo.cpp
|
2015-02-02 18:53:21 +00:00
|
|
|
DebugInfoMetadata.cpp
|
2011-10-04 18:22:24 +00:00
|
|
|
DebugLoc.cpp
|
2014-04-12 14:26:59 +00:00
|
|
|
DiagnosticInfo.cpp
|
|
|
|
DiagnosticPrinter.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Dominators.cpp
|
|
|
|
Function.cpp
|
2011-10-04 18:22:24 +00:00
|
|
|
GCOV.cpp
|
2010-01-27 20:44:12 +00:00
|
|
|
GVMaterializer.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Globals.cpp
|
2010-01-27 20:44:12 +00:00
|
|
|
IRBuilder.cpp
|
2014-01-09 02:39:45 +00:00
|
|
|
IRPrintingPasses.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
InlineAsm.cpp
|
|
|
|
Instruction.cpp
|
|
|
|
Instructions.cpp
|
|
|
|
IntrinsicInst.cpp
|
2009-06-30 00:48:55 +00:00
|
|
|
LLVMContext.cpp
|
2010-03-21 21:17:34 +00:00
|
|
|
LLVMContextImpl.cpp
|
2013-11-09 12:26:54 +00:00
|
|
|
LegacyPassManager.cpp
|
2014-04-12 14:26:59 +00:00
|
|
|
MDBuilder.cpp
|
2014-01-07 21:19:40 +00:00
|
|
|
Mangler.cpp
|
2009-07-28 21:49:47 +00:00
|
|
|
Metadata.cpp
|
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.)
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@223802 91177308-0d34-0410-b5e6-96231b3b80d8
2014-12-09 18:38:53 +00:00
|
|
|
MetadataTracking.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Module.cpp
|
2015-05-08 00:42:26 +00:00
|
|
|
Operator.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Pass.cpp
|
2013-11-13 01:12:08 +00:00
|
|
|
PassManager.cpp
|
2010-07-20 18:39:06 +00:00
|
|
|
PassRegistry.cpp
|
[Statepoints 3/4] Statepoint infrastructure for garbage collection: SelectionDAGBuilder
This is the third patch in a small series. It contains the CodeGen support for lowering the gc.statepoint intrinsic sequences (223078) to the STATEPOINT pseudo machine instruction (223085). The change also includes the set of helper routines and classes for working with gc.statepoints, gc.relocates, and gc.results since the lowering code uses them.
With this change, gc.statepoints should be functionally complete. The documentation will follow in the fourth change, and there will likely be some cleanup changes, but interested parties can start experimenting now.
I'm not particularly happy with the amount of code or complexity involved with the lowering step, but at least it's fairly well isolated. The statepoint lowering code is split into it's own files and anyone not working on the statepoint support itself should be able to ignore it.
During the lowering process, we currently spill aggressively to stack. This is not entirely ideal (and we have plans to do better), but it's functional, relatively straight forward, and matches closely the implementations of the patchpoint intrinsics. Most of the complexity comes from trying to keep relocated copies of values in the same stack slots across statepoints. Doing so avoids the insertion of pointless load and store instructions to reshuffle the stack. The current implementation isn't as effective as I'd like, but it is functional and 'good enough' for many common use cases.
In the long term, I'd like to figure out how to integrate the statepoint lowering with the register allocator. In principal, we shouldn't need to eagerly spill at all. The register allocator should do any spilling required and the statepoint should simply record that fact. Depending on how challenging that turns out to be, we may invest in a smarter global stack slot assignment mechanism as a stop gap measure.
Reviewed by: atrick, ributzka
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@223137 91177308-0d34-0410-b5e6-96231b3b80d8
2014-12-02 18:50:36 +00:00
|
|
|
Statepoint.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Type.cpp
|
2012-08-03 00:30:35 +00:00
|
|
|
TypeFinder.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Use.cpp
|
2011-01-16 08:10:57 +00:00
|
|
|
User.cpp
|
2008-09-22 01:08:49 +00:00
|
|
|
Value.cpp
|
|
|
|
ValueSymbolTable.cpp
|
|
|
|
ValueTypes.cpp
|
|
|
|
Verifier.cpp
|
2015-02-11 03:28:02 +00:00
|
|
|
|
|
|
|
ADDITIONAL_HEADER_DIRS
|
|
|
|
${LLVM_MAIN_INCLUDE_DIR}/llvm/IR
|
2008-09-22 01:08:49 +00:00
|
|
|
)
|
2012-06-24 03:48:29 +00:00
|
|
|
|
2012-06-24 13:32:01 +00:00
|
|
|
add_dependencies(LLVMCore intrinsics_gen)
|