6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-06-30 20:24:32 +00:00
Code Issues Projects Releases Wiki Activity

[Statepoints 1/4] Statepoint infrastructure for garbage collection: IR Intrinsics

Browse Source 
The statepoint intrinsics are intended to enable precise root tracking through the compiler as to support garbage collectors of all types. The addition of the statepoint intrinsics to LLVM should have no impact on the compilation of any program which does not contain them. There are no side tables created, no extra metadata, and no inhibited optimizations.

A statepoint works by transforming a call site (or safepoint poll site) into an explicit relocation operation. It is the frontend's responsibility (or eventually the safepoint insertion pass we've developed, but that's not part of this patch series) to ensure that any live pointer to a GC object is correctly added to the statepoint and explicitly relocated. The relocated value is just a normal SSA value (as seen by the optimizer), so merges of relocated and unrelocated values are just normal phis. The explicit relocation operation, the fact the statepoint is assumed to clobber all memory, and the optimizers standard semantics ensure that the relocations flow through IR optimizations correctly.

This is the first patch in a small series.  This patch contains only the IR parts; the documentation and backend support will be following separately.  The entire series can be seen as one combined whole in http://reviews.llvm.org/D5683.

Reviewed by: atrick, ributzka





git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@223078 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Philip Reames
2014-12-01 21:18:12 +00:00
parent b043278834
commit 204e21b51a
4 changed files with 151 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

81
lib/IR/Verifier.cpp
View File

@ -2559,7 +2559,88 @@ void Verifier::visitIntrinsicFunctionCall(Intrinsic::ID ID, CallInst &CI) {
Assert1(isa<ConstantInt>(CI.getArgOperand(1)),
"llvm.invariant.end parameter #2 must be a constant integer", &CI);
break;
case Intrinsic::experimental_gc_statepoint: {
// target, # call args = 0, # deopt args = 0, #gc args = 0 -> 4 args
assert(CI.getNumArgOperands() >= 4 &&
"not enough arguments to statepoint");
for (User* U : CI.users()) {
const CallInst* GCRelocCall = cast<const CallInst>(U);
const Function *GCRelocFn = GCRelocCall->getCalledFunction();
Assert1(GCRelocFn && GCRelocFn->isDeclaration() &&
(GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_result_int ||
GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_result_float ||
GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_result_ptr ||
GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_relocate),
"gc.result or gc.relocate are the only value uses of statepoint", &CI);
if (GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_result_int ||
GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_result_float ||
GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_result_ptr ) {
Assert1(GCRelocCall->getNumArgOperands() == 1, "wrong number of arguments", &CI);
Assert2(GCRelocCall->getArgOperand(0) == &CI, "connected to wrong statepoint", &CI, GCRelocCall);
} else if (GCRelocFn->getIntrinsicID() == Intrinsic::experimental_gc_relocate) {
Assert1(GCRelocCall->getNumArgOperands() == 3, "wrong number of arguments", &CI);
Assert2(GCRelocCall->getArgOperand(0) == &CI, "connected to wrong statepoint", &CI, GCRelocCall);
} else {
llvm_unreachable("unsupported use type - how'd we get past the assert?");
}
}
// Note: It is legal for a single derived pointer to be listed multiple
// times. It's non-optimal, but it is legal. It can also happen after
// insertion if we strip a bitcast away.
// Note: It is really tempting to check that each base is relocated and
// that a derived pointer is never reused as a base pointer. This turns
// out to be problematic since optimizations run after safepoint insertion
// can recognize equality properties that the insertion logic doesn't know
// about. See example statepoint.ll in the verifier subdirectory
break;
}
case Intrinsic::experimental_gc_result_int:
case Intrinsic::experimental_gc_result_float:
case Intrinsic::experimental_gc_result_ptr: {
Assert1(CI.getNumArgOperands() == 1, "wrong number of arguments", &CI);
// Are we tied to a statepoint properly?
CallSite StatepointCS(CI.getArgOperand(0));
const Function *StatepointFn = StatepointCS.getCalledFunction();
Assert2(StatepointFn && StatepointFn->isDeclaration() &&
StatepointFn->getIntrinsicID() == Intrinsic::experimental_gc_statepoint,
"token must be from a statepoint", &CI, CI.getArgOperand(0));
break;
}
case Intrinsic::experimental_gc_relocate: {
// Some checks to ensure gc.relocate has the correct set of
// parameters. TODO: we can make these tests much stricter.
Assert1(CI.getNumArgOperands() == 3, "wrong number of arguments", &CI);
// Are we tied to a statepoint properly?
CallSite StatepointCS(CI.getArgOperand(0));
const Function *StatepointFn =
StatepointCS.getInstruction() ? StatepointCS.getCalledFunction() : NULL;
Assert2(StatepointFn && StatepointFn->isDeclaration() &&
StatepointFn->getIntrinsicID() == Intrinsic::experimental_gc_statepoint,
"token must be from a statepoint", &CI, CI.getArgOperand(0));
// Both the base and derived must be piped through the safepoint
Value* Base = CI.getArgOperand(1);
Assert1( isa<ConstantInt>(Base), "must be integer offset", &CI);
Value* Derived = CI.getArgOperand(2);
Assert1( isa<ConstantInt>(Derived), "must be integer offset", &CI);
const int BaseIndex = cast<ConstantInt>(Base)->getZExtValue();
const int DerivedIndex = cast<ConstantInt>(Derived)->getZExtValue();
// Check the bounds
Assert1(0 <= BaseIndex &&
BaseIndex < (int)StatepointCS.arg_size(),
"index out of bounds", &CI);
Assert1(0 <= DerivedIndex &&
DerivedIndex < (int)StatepointCS.arg_size(),
"index out of bounds", &CI);
break;
}
};
}
void DebugInfoVerifier::verifyDebugInfo() {