unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: a.rottmann@gmx.at, 351693-forwarded@bugs.debian.org,
	Steve Langasek <vorlon@debian.org>,
	guile-devel@gnu.org
Subject: Re: Bug#351693: guile-1.6: builds on ia64, but causes other packages to FTBFS?
Date: Fri, 14 Jul 2006 20:36:20 -0700	[thread overview]
Message-ID: <871wsnmte3.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87lkrxo19r.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 16 Jun 2006 11:14:40 +0100")

Neil Jerram <neil@ossau.uklinux.net> writes:

> Is anyone already working on this?  If not, I'll take a look.

I looked around a bit last night and found some relevant discussions:

  http://gcc.gnu.org/ml/gcc/2002-07/msg01417.html
  http://www.gelato.unsw.edu.au/archives/linux-ia64/0109/2178.html

I also came across this, which suggests that adding a dummy setjmp
before the getcontext call might help:

  http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/144939

So I tried adding a dummy setjmp call (which isn't actually executed)
right before getcontext in continuations.c, and that does fix the
illegal instruction when executing (call/cc (lambda (c) (c #t))).

However, without having a better understanding about what's actually
happening, I'm not inclined to treat this as a correct solution yet.

Can anyone else comment more conclusively?

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-07-15  3:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060601010806.GA8248@mauritius.dodds.net>
2006-06-04 20:36 ` Bug#351693: guile-1.6: builds on ia64, but causes other packages to FTBFS? Rob Browning
2006-06-16 10:14   ` Neil Jerram
2006-07-15  3:36     ` Rob Browning [this message]
2006-07-15 21:50       ` Rob Browning
2006-07-19  7:05         ` Rob Browning

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=871wsnmte3.fsf@raven.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=351693-forwarded@bugs.debian.org \
    --cc=a.rottmann@gmx.at \
    --cc=guile-devel@gnu.org \
    --cc=vorlon@debian.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).