search for: calinst

...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 separate issues here: > > 1. catching exceptions from function calls > 2. catching exceptions from "non call" instructions like divides, etc. > > The LLVM IR, as it stands now, is expressive enough t...

On Thu, 5 Apr 2007, Nicolas Geoffray wrote: > On top of this execution environment we have implemented a java virtual > machine and a .net virtual machine. They > are both functional and we achieve reasonable performance (1/3 of IBM's > JVM or Mono). Cool. > This algorithm does not work with llvm because creating labels (which > correspond to creating basic blocks) does not

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 of remaining bugs 2. Extending the JIT to emit the EH table...

Hi everyone, After some time hacking on llvm, let me introduce myself :) I'm a PhD student at the French university Pierre et Marie Curie in Paris. I work on a project called the "Virtual Virtual Machine" project. You can find some (dated) information on the website http://vvm.lip6.fr. Basically it's a "low level virtual machine" :) with a just in time compiler