Displaying 4 results from an estimated 4 matches for "unwindbb".
Did you mean:
unwind
2007 Apr 06
1
[LLVMdev] Integrating LLVM in an existing project
...rk.
Also, I suppose you might need to uncomment this bit in llvm-backend.cpp
as well:
// Disabled until PR1224 is resolved.
//if (flag_exceptions)
// Args.push_back("--enable-eh");
Some comments on the patch:
(1)
new UnreachableInst(CurBB);
+ } else {
+ new UnwindInst(UnwindBB);
}
-#endif
+#else
new UnwindInst(UnwindBB);
+#endif
This avoid generating an unwind instruction straight after an unreachable
instruction, i.e. two terminators in a row.
(2)
- FuncCPPPersonality = cast<Function>(
+ FuncCPPPersonality =
TheModule->getOrInsertFunction(&q...
2007 Apr 06
0
[LLVMdev] Integrating LLVM in an existing project
On Fri, 6 Apr 2007, Nicolas Geoffray wrote:
> Like you say, it's not functional for non-calls instructions. Besides,
> having to change all CalInst to InvokeInst is just too much pain in our
> current vm.
ok.
> Actually, why is it missing? What's the difference between the code
> generator and the JIT?
There are two things missing:
1. Testing and working out the set
2010 Nov 09
1
[LLVMdev] uninitialized value warnings: LLVMParser.cpp
...lvm::LLParser::ParseInvoke(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’:
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3316: warning: ‘NormalBB’ may be used uninitialized in this function
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3316: warning: ‘UnwindBB’ may be used uninitialized in this function
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseSwitch(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’:
/Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3224: warning...
2007 Apr 06
2
[LLVMdev] Integrating LLVM in an existing project
Hi Chris,
Chris Lattner wrote:
>> We can not use current exception handling in llvm, see
>> http://www.nondot.org/sabre/LLVMNotes/ExceptionHandlingChanges.txt.
>>
>
> Why not?
>
>
Like you say, it's not functional for non-calls instructions. Besides,
having to change
all CalInst to InvokeInst is just too much pain in our current vm.
> There are two