[pypy-dev] llvm2 update

[Chris Lattner]

On Fri, 15 Jul 2005, Richard Emslie wrote:
> Of the above I am guess that exceptions are most interesting.  The unwind / 
> invoke operations of llvm fits this quite well, but still need somewhere to 
> store the exception and do matching - unless I missed something?  Any 
> thoughts / takers?

This is generally done with global variables.  The C++ front-end basically 
generates code like this:

   C++:  throw 42;

Pseudo LLVM code:
    int *E = allocate_exception_memory(4);
    *E = 42;
    add_to_current_exception_stack(E);
    unwind

I imagine that something similar should work for pypy.

-Chris

-- 
http://nondot.org/sabre/
http://llvm.org/