search for: tart_eh_personality

...ction? Since my object representations are not C++-like, I am not using any of the cxa_* C++ library functions. Instead, my code calls the _Unwind functions directly, and I have my own personality function (which can be viewed here: http://code.google.com/p/tart/source/browse/trunk/runtime/lib/tart_eh_personality.c) My compiler generates the list of filter parameters as pointers to Type objects. In the personality function, it examines each such pointer and does an IsSubclass test. The action code returned by the personality function is a simple integer index (0, 1, 2, ...etc) which represents the num...

...n invoke { } @"throwSomething"() to label %endTry unwind label %catch catch: ;; Catch and decode the exception %eh_ptr = call i8* @llvm.eh.exception() %eh_action = call i32 (i8*, i8*, ...)* @llvm.eh.selector.i32( i8* %eh_ptr, i8* bitcast (i32 (i32, i32, i64, i8*, i8*)* @__tart_eh_personality to i8*), %tart.reflect.Type* @tart.core.InvalidArgumentException.type, %tart.reflect.Type* @tart.core.Throwable.type) ;; subtract offset of UnwindExceptInfo member within class Throwable %0 = bitcast i8* %eh_ptr to [0 x i8]* %eh_throwable = getelementptr [0 x i8]* %0, i32 0, i32...

On 07/05/2011 08:42 PM, Talin wrote: > 2) However, I don't think we should do this unless we can identify at > least one other customer other than myself - mainly because I don't want > the design decisions to be too tailored to my specific use cases. Pure would be another candidate, so I'd be interested in such a toolbox as well, especially in the synchronization primitives

I've been looking into a new way to implement exception handling in LLVM. The current model has many disadvantages, in my opinion. I try to address them with this proposal. I also try to make exception handling much more understandable to the normal human reader. :-) Any new proposal will need to address all present and future languages' exception handling methodologies. I