From: Taahir Ahmed <ahmed.taahir@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Exception-safety for C++ code integrated with Guile.
Date: Tue, 24 Feb 2015 13:59:24 -0600 [thread overview]
Message-ID: <2825010.3hA8aj4kt9@basis> (raw)
In-Reply-To: <83bnkj6t28.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Alternatively, it looks like both gcc and clang export the ia64 c++ exception
api as <unwind.h>. (Note that it is called "ia64" as a historical artifact,
since it was originally developed for ia64).
It looks like it should be easy to have some sj/lj wrappers that use the
system sj/lj for register saving and jumping, and the <unwind.h> interface to
destroy intermediate frames.
I'll try to hack up a solution based on this.
Taahir
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-24 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 21:59 Exception-safety for C++ code integrated with Guile Taahir Ahmed
2015-02-24 18:52 ` Eli Zaretskii
2015-02-24 19:21 ` Taahir Ahmed
2015-02-24 19:36 ` Eli Zaretskii
2015-02-24 19:59 ` Taahir Ahmed [this message]
2015-03-10 21:15 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2825010.3hA8aj4kt9@basis \
--to=ahmed.taahir@gmail.com \
--cc=eliz@gnu.org \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).