Rename variables in gc_relocate related functions to follow LLVM's naming conventions.

Summary:
This patch is to rename some variables to CamelCase in gc_relocate
related functions. There is no functionality change.

Patch by Chen Li!

Reviewers: reames, AndyAyers, sanjoy

Reviewed By: sanjoy

Subscribers: llvm-commits

Differential Revision: http://reviews.llvm.org/D9681

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@237069 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Sanjoy Das
2015-05-11 23:47:27 +00:00
parent 66c6a4c240
commit aa1c57e324
2 changed files with 47 additions and 47 deletions

View File

@@ -3309,17 +3309,17 @@ void Verifier::visitIntrinsicFunctionCall(Intrinsic::ID ID, CallInst &CI) {
"gc relocate on unwind path incorrectly linked to the statepoint",
&CI);
const BasicBlock *invokeBB =
const BasicBlock *InvokeBB =
ExtractValue->getParent()->getUniquePredecessor();
// Landingpad relocates should have only one predecessor with invoke
// statepoint terminator
Assert(invokeBB, "safepoints should have unique landingpads",
Assert(InvokeBB, "safepoints should have unique landingpads",
ExtractValue->getParent());
Assert(invokeBB->getTerminator(), "safepoint block should be well formed",
invokeBB);
Assert(isStatepoint(invokeBB->getTerminator()),
"gc relocate should be linked to a statepoint", invokeBB);
Assert(InvokeBB->getTerminator(), "safepoint block should be well formed",
InvokeBB);
Assert(isStatepoint(InvokeBB->getTerminator()),
"gc relocate should be linked to a statepoint", InvokeBB);
}
else {
// In all other cases relocate should be tied to the statepoint directly.
@@ -3332,8 +3332,8 @@ void Verifier::visitIntrinsicFunctionCall(Intrinsic::ID ID, CallInst &CI) {
// Verify rest of the relocate arguments
GCRelocateOperands ops(&CI);
ImmutableCallSite StatepointCS(ops.getStatepoint());
GCRelocateOperands Ops(&CI);
ImmutableCallSite StatepointCS(Ops.getStatepoint());
// Both the base and derived must be piped through the safepoint
Value* Base = CI.getArgOperand(1);