From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Taahir Ahmed Newsgroups: gmane.lisp.guile.devel Subject: Re: Exception-safety for C++ code integrated with Guile. Date: Tue, 24 Feb 2015 13:21:48 -0600 Message-ID: <4194214.B3z6dDOsXA@basis> References: <474913203.jcqxqasMgP@basis> <83bnkj6t28.fsf@gnu.org> Reply-To: ahmed.taahir@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2155883.Sz9Ly5hKX0"; micalg="pgp-sha1"; protocol="application/pgp-signature" X-Trace: ger.gmane.org 1424805732 17660 80.91.229.3 (24 Feb 2015 19:22:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Feb 2015 19:22:12 +0000 (UTC) Cc: guile-devel@gnu.org To: Eli Zaretskii Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Feb 24 20:22:11 2015 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YQL3a-00046v-Ja for guile-devel@m.gmane.org; Tue, 24 Feb 2015 20:22:10 +0100 Original-Received: from localhost ([::1]:51005 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQL3Z-0000CC-Tz for guile-devel@m.gmane.org; Tue, 24 Feb 2015 14:22:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49100) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQL3W-00007N-T9 for guile-devel@gnu.org; Tue, 24 Feb 2015 14:22:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YQL3V-0007HM-Rk for guile-devel@gnu.org; Tue, 24 Feb 2015 14:22:06 -0500 Original-Received: from mail-oi0-x235.google.com ([2607:f8b0:4003:c06::235]:34863) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQL3L-0007GI-Rf; Tue, 24 Feb 2015 14:21:55 -0500 Original-Received: by mail-oi0-f53.google.com with SMTP id u20so21212154oif.12; Tue, 24 Feb 2015 11:21:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:reply-to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-type; bh=nafgmEepMfdDoojyu/8gHp8KkpObcnFAAbCW3oEulGw=; b=sEamk1gJFC+INlFW3a5xVHazyuA3awNfFoxtjycgT99zJdQFwt3jUmsqoiFIgpvH5K 6WsfXlpmlvjxTosqh6fw3SxUfvrSiwPJhaIGkzS3jj1OsPt2Cv5CQA0+4ft5YgLkWU/T nagBgXNiDR2xjcAZ8bJ4deT/sShNrLj01PVb/Snk8DJTCBBt4u8CZpFTtTeMSGYTRQxO NDfMKRE0B4s4wRdfdFhkREQGzkdv8X5nhRqg3db9b4DWlpjOxXZt1OURC5ING5SRfk8X ogAPBtkArO5tFMk6t0gM/qInOTs9Zt+Y47QP63peHj+7Rcz3LySOh50R5HzQUiDmitfy qkzg== X-Received: by 10.202.218.135 with SMTP id r129mr11882430oig.26.1424805713431; Tue, 24 Feb 2015 11:21:53 -0800 (PST) Original-Received: from basis.localnet (nat-165-91-12-5.tamulink.tamu.edu. [165.91.12.5]) by mx.google.com with ESMTPSA id vc7sm16504258obb.28.2015.02.24.11.21.52 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2015 11:21:53 -0800 (PST) User-Agent: KMail/4.14.3 (Linux/3.16.5-gentoo; KDE/4.14.3; x86_64; ; ) In-Reply-To: <83bnkj6t28.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c06::235 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:17674 Archived-At: --nextPart2155883.Sz9Ly5hKX0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" > mingw.org's MinGW uses DWARF exception handling. Perhaps you are > thinking of MinGW64, which (AFAIK) indeed uses eh by default, but can= > be configured to use DWARF. I was under the impression that MinGW only used setjump/longjump except= ion=20 handling, with plans to move to Windows SEH. Either way, it's neither = here=20 nor there. > As for libunwind, are you sure it supports enough platforms to be a > useful alternative? AFAIK, the last official release supports only > IA-64, and even the current development version in git repo basically= > supports GNU/Linux and almost nothing else (2 FreeBSD targets and 1 o= n > HP-UX). The documentation of the last official release (v1.1, in 2012) only men= tions=20 ia64, but it appears to actually support the same list of platforms as = the=20 current version. From=20looking at the libunwind source, the only os-dependent code is a s= ingle=20 function for looking through an elf image. The rest of the code is wri= tten=20 once for each architecture (more specifically, once for each=20 architecture/calling convention tuple). What are the platforms that Guile supports? (I can't find a comprehensi= ve list=20 anywhere). In _scm.h, I can see special casing of sj/lj for vms, cray(= !!),=20 and ia64. There's no need to change the behavior for vms and cray. Th= e ia64=20 special casing is simply to force all registers to be saved, which is e= asy to=20 handle. It seems reasonable that all other cases will be covered by li= bunwind=20 (or at least, libunwind with some small modifications). Of course, if testing uncovers an os/arch tuple that doesn't work, one = can=20 simply fall back to the standard system sj/lj, and not having C++ clean= up=20 behavior on those platforms. --nextPart2155883.Sz9Ly5hKX0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABAgAGBQJU7M9QAAoJEP0dGB2mOaLGo6YH/0ZMEU8dQAPMdCcwyxDghYrD +gtsOeopsQQnC5oMOnRRCwuTwMZpJKkGYodbcTymI9k7hpUc++iAucJyS2l3jDRN 7qfHFGDzLQvNxT6nzzIBEPcxGDrWZc7f6SbpUPANS/Xn3476Sh6hsRh8jzCTNBJ1 jJus2RID5c7ufZNM4LkVfxvc+yxDhPak8S2QW0oXgusnLOutQp7dUNYbTPsRAePz COIt5mvZ2aGpIIk9O1UgvaytYqOybVBvXkwqN3zn8M7dPo5iF2vHh8SHHeejBLBB bzg0gTe6cfNzsS1wnU/OIfPu/qSf8kGXOVzqFUW1w+uMbV+6vHQJnG/jaTOUWrA= =1O4m -----END PGP SIGNATURE----- --nextPart2155883.Sz9Ly5hKX0--