Displaying 5 results from an estimated 5 matches for "destbb".
Did you mean:
dest
2004 Dec 07
1
[LLVMdev] Question adding dummy basic blocks
...anwhile we generate a new basic block and unconditional branch which is from C to B.
Finally, We got some problems due to PHINODE. I knew the reason, but I failed to fix it.
The code is like the following
if( TI->getNumSuccessors() ==1){
BasicBlock *TIBB=TI->getParent();
BasicBlock *DestBB=TI->getSuccessor(0);
BasicBlock *NewBB = new BasicBlock(TIBB->getName()+DestBB->getName()+"dummy_bb",&F);
new BranchInst(DestBB, NewBB);
BranchInst *NewBr = new BranchInst(DestBB, NewBB, V_dummy);
ReplaceInstWithInst(TI, NewBr);
// the following code, we are...
2010 Nov 09
1
[LLVMdev] uninitialized value warnings: LLVMParser.cpp
...vm::LLParser::ParseSwitch(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’:
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3224: warning: ‘DefaultBB’ may be used uninitialized in this function
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3239: warning: ‘DestBB’ may be used uninitialized in this function
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseIndirectBr(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’:
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3281: war...
2011 Mar 28
0
[LLVMdev] [RC3] Status on Cygwin-1.7
.../AsmParser'
llvm[0]: Compiling LLParser.cpp for Release build
/cygdrive/e/llvm/llvm/lib/AsmParser/LLParser.cpp: In member function
‘bool llvm::LLParser::ParseSwitch(llvm::Instruction*&,
llvm::LLParser::PerFunctionState&)’:
/cygdrive/e/llvm/llvm/lib/AsmParser/LLParser.cpp:3231: warning:
‘DestBB’ may be used uninitialized in this function
/cygdrive/e/llvm/llvm/lib/AsmParser/LLParser.cpp: In member function
‘bool llvm::LLParser::ParseIndirectBr(llvm::Instruction*&,
llvm::LLParser::PerFunctionState&)’:
/cygdrive/e/llvm/llvm/lib/AsmParser/LLParser.cpp:3273: warning:
‘DestBB’ may be us...
2008 Apr 16
0
[LLVMdev] Being able to know the jitted code-size before emitting
...ddMBB(NextBB)
> .addImm(CC).addReg(CCReg);
> Br.MI = &MBB->back();
> - BBSizes[MBB->getNumber()] += ARM::GetInstSize(&MBB->back());
> + BBSizes[MBB->getNumber()] += TII->GetInstSize(&MBB->back());
> BuildMI(MBB, TII->get(Br.UncondBr)).addMBB(DestBB);
> - BBSizes[MBB->getNumber()] += ARM::GetInstSize(&MBB->back());
> + BBSizes[MBB->getNumber()] += TII->GetInstSize(&MBB->back());
> unsigned MaxDisp = getUnconditionalBrDisp(Br.UncondBr);
> ImmBranches.push_back(ImmBranch(&MBB->back(), MaxDisp, fals...
2008 Apr 15
4
[LLVMdev] Being able to know the jitted code-size before emitting
OK, here's a new patch that adds the infrastructure and the
implementation for X86, ARM and PPC of GetInstSize and GetFunctionSize.
Both functions are virtual functions defined in TargetInstrInfo.h.
For X86, I moved some commodity functions from X86CodeEmitter to
X86InstrInfo.
What do you think?
Nicolas
Evan Cheng wrote:
>
> I think both of these belong to TargetInstrInfo. And