llvm dev - Jul 2013 - [LLVMdev] setjmp/longjmp exception handling: how?

Dear list,

I want to add SJLJ exception handling to my frontend. Unfortunately,
there doesn't seem to be any examples in the documentation as to how
to use the intrinsics

@llvm.eh.sjlj.setjmp
@llvm.eh.sjlj.longjmp
@llvm.eh.sjlj.lsda
@llvm.eh.sjlj.callsite

Is there a way to force Clang to use SJLJ exception handling for C++? That
way I would be able to look at its output to learn how to use them correctly.

Otherwise, how should I go about finding out how to implement SJLJ exception
handling in my frontend?

Thanks!
Nicolas

I strongly advise you not to use SjLj exception handling. Use
zero-cost-exceptions via DWARF instead.

If you really want to pursue sjlj anyway, look at the ARM backend. It uses them
for darwin targets.

-Jim

On Jul 12, 2013, at 9:09 AM, Nicolas Ojeda Bar <N.Ojeda.Bar at
dpmms.cam.ac.uk> wrote:
> Dear list,
> 
> I want to add SJLJ exception handling to my frontend. Unfortunately,
> there doesn't seem to be any examples in the documentation as to how
> to use the intrinsics
> 
> @llvm.eh.sjlj.setjmp
> @llvm.eh.sjlj.longjmp
> @llvm.eh.sjlj.lsda
> @llvm.eh.sjlj.callsite
> 
> Is there a way to force Clang to use SJLJ exception handling for C++? That
> way I would be able to look at its output to learn how to use them
correctly.
> 
> Otherwise, how should I go about finding out how to implement SJLJ
exception
> handling in my frontend?
> 
> Thanks!
> Nicolas
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130712/8ab67146/attachment.html>

Jim Grosbach <grosbach at apple.com> writes:
> I strongly advise you not to use SjLj exception handling. Use
> zero-cost-exceptions via DWARF instead.
On Windows, DWARF EH doesn't work when there are stack frames not
compiled with DWARF EH support (i.e. OS code that invokes user-provided
callbacks, a common practice on Windows.)