From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Preparing for a 1.6.8 release.
Date: Wed, 19 Oct 2005 15:59:13 -0700 [thread overview]
Message-ID: <87hdbdnmf2.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <200510192231.PAA27954@hpsje.cup.hp.com> (Steve Ellcey's message of "Wed, 19 Oct 2005 15:31:11 -0700 (PDT)")
Steve Ellcey <sje@cup.hp.com> writes:
> Well the test for IA64 and not HP-UX would be "defined(__ia64) &&
> !defined(__hpux)". __hpux and __ia64 are defined by both the HP
> compilers and GCC on IA64 HP-UX. __hpux__ and __ia64__ are only defined
> by GCC. IA64 Linux GCC defines __ia64 and __ia64__ but not any of the
> hpux macros.
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?
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
next prev parent reply other threads:[~2005-10-19 22:59 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 [this message]
2005-10-19 23:22 ` Steve Ellcey
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=87hdbdnmf2.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).