search for: tp21087203p21175147

...t; does nothing at all - it compiles into a no-op. So you have to use the lower-level functions in libgcc. I've never figured out how to get it working, sorry. But there may be helpful information in that thread. Matt -- View this message in context: http://www.nabble.com/Unwinds-gone-missing-tp21087203p21175147.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

On Friday 19 December 2008 07:45:27 Talin wrote: > I understand that "unwind" is currently unimplemented... Is it? I was just reading the documentation about LLVM's exception handling and it sounded ideal for my needs. How much of it does not work as the docs imply? > and will remain so for the forseeable future... Surely C++-style exception handling is a priority? What

...So > you have > to use the lower-level functions in libgcc. I've never figured out > how to > get it working, sorry. But there may be helpful information in that > thread. > > Matt > -- > View this message in context: http://www.nabble.com/Unwinds-gone-missing-tp21087203p21175147.html > Sent from the LLVM - Dev mailing list archive at Nabble.com. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- next...

After much delay, I have finally reached the point in my work where I need to implement some kind of exception handling. I understand that "unwind" is currently unimplemented and will remain so for the forseeable future. In the mean time, are there any examples available for implementing Java or Python-style exceptions using __cxa_throw or something similar? I've read and