From: Steve Ellcey <sje@cup.hp.com>
Cc: guile-devel@gnu.org
Subject: Re: Preparing for a 1.6.8 release.
Date: Wed, 19 Oct 2005 16:22:40 -0700 (PDT) [thread overview]
Message-ID: <200510192322.QAA28096@hpsje.cup.hp.com> (raw)
In-Reply-To: <87hdbdnmf2.fsf@trouble.defaultvalue.org>
> So what code should be used on HP-UX? Should the code in gc_os_dep.c
> that's currently guarded by IA64 be enabled or not, and should gc.c
> and continuations.c be doing something different for HP-UX, or nothing
> at all?
Well, I am not sure. There seem to be two ways to attack this, create
some HP-UX specific code for continuations.c and gc.c, which would be to
replace the access of ucontext_t with calls and then set IA64 in
gc_os_dep.c and do more HP-UX specific stuff in that file. Or bail out
of the continuations.c and gc.c changes (use the default case) and just
use more generic code. I am not sure what the right way to go is.
I don't have the HP-UX specific code for continuations.c and gc.c at
hand, my first thought was to just skip that code and use the generic C
code. That is why I was wondering if we wanted to punt on 1.6.8. And,
to add one more complication, the accessor functions that I would use to
replace the IA64 Linux code are not in libc, but in a library called
libuca.so so that library would need to be linked in with guile. I
don't know if that complicates things or not.
I am not sure exactly what schedule 1.6.8 is on but I will be down from
tomorrow afternoon until Monday because of an office move over the
weekend.
Steve Ellcey
sje@cup.hp.com
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-19 23:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 2:11 Preparing for a 1.6.8 release Rob Browning
2005-10-16 19:35 ` Steve Ellcey
2005-10-19 21:08 ` Rob Browning
2005-10-19 21:25 ` Steve Ellcey
2005-10-19 21:54 ` Rob Browning
2005-10-19 22:31 ` Steve Ellcey
2005-10-19 22:59 ` Rob Browning
2005-10-19 23:22 ` Steve Ellcey [this message]
2005-10-19 23:39 ` Rob Browning
2005-10-19 23:45 ` Steve Ellcey
2005-10-16 22:46 ` Kevin Ryde
2005-10-16 22:59 ` Rob Browning
2005-10-18 7:31 ` Ludovic Courtès
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=200510192322.QAA28096@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--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).