[pypy-dev] llvm2 update
sabre at nondot.org
Fri Jul 15 23:47:16 CEST 2005
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;
I imagine that something similar should work for pypy.
More information about the Pypy-dev