From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ludo@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) Newsgroups: gmane.lisp.guile.devel Subject: Re: [PATCH] Fix continuation problems on IA64. Date: Fri, 09 May 2008 10:15:26 +0200 Message-ID: <87lk2jhp0h.fsf@gnu.org> References: <87k5i5d6ei.fsf@ossau.uklinux.net> <87y76ksglg.fsf@gnu.org> <8763tomqn7.fsf@ossau.uklinux.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1210321012 7155 80.91.229.12 (9 May 2008 08:16:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 9 May 2008 08:16:52 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Fri May 09 10:17:27 2008 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JuNnC-0004or-Me for guile-devel@m.gmane.org; Fri, 09 May 2008 10:17:26 +0200 Original-Received: from localhost ([127.0.0.1]:50367 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuNmU-0002gE-7V for guile-devel@m.gmane.org; Fri, 09 May 2008 04:16:42 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JuNlU-000271-2S for guile-devel@gnu.org; Fri, 09 May 2008 04:15:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JuNlS-00025C-Cz for guile-devel@gnu.org; Fri, 09 May 2008 04:15:39 -0400 Original-Received: from [199.232.76.173] (port=43852 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuNlS-00024p-6f for guile-devel@gnu.org; Fri, 09 May 2008 04:15:38 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:51755 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JuNlR-0004He-SF for guile-devel@gnu.org; Fri, 09 May 2008 04:15:38 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JuNlP-0004gs-H2 for guile-devel@gnu.org; Fri, 09 May 2008 08:15:35 +0000 Original-Received: from 193.50.110.171 ([193.50.110.171]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 May 2008 08:15:35 +0000 Original-Received: from ludo by 193.50.110.171 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 May 2008 08:15:35 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 38 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 193.50.110.171 X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 21 =?iso-8859-1?Q?Flor=E9al?= an 216 de la =?iso-8859-1?Q?R=E9volution?= X-PGP-Key-ID: 0xEA52ECF4 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 821D 815D 902A 7EAB 5CEE D120 7FBA 3D4F EB1F 5364 X-OS: i686-pc-linux-gnu User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) Cancel-Lock: sha1:VicHznUO+lcJUiyF9Fw8wy9s8vs= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:7225 Archived-At: Hi, Neil Jerram writes: > ludo@gnu.org (Ludovic Courtès) writes: >> This breaks ABI compatibility on IA64, but if Guile wasn't usable on >> IA64 (was it?) that's probably not a problem. > > Good point, and I don't think it was completely unusable before, so > this could be an issue. The problems were sufficient to break > Lilypond on IA64, but many simpler programs could have been fine. > > Who is ABI compatibility an issue for? If it's only the distros, > we're probably OK, as I believe they won't have promoted something > that failed "make check". If we change the ABI, we should increase `LIBGUILE_INTERFACE_CURRENT' and set `AGE' to zero because it's not going to be backward-compatible---and we can't do that only for IA64, unfortunately... > For people building their own Guile libs, can we cover this by a > sentence in the next release notes, to say that programs using > scm_i_thread should be recompiled? Programs necessarily access it, through `SCM_I_CURRENT_THREAD', etc. > I'm happy with adding SCM_NORETURN; but why the SCM_API? I don't > think a libguile application should call scm_ia64_longjmp itself, so > do not intend to document it. Right, but `SCM_API' is just `extern' (except on Windows), which is "normal" in such a declaration; and whether declared `extern' or not, the symbol will be exported anyway. Thanks, Ludovic.