From: David Mosberger <davidm@napali.hpl.hp.com>
Cc: David Mosberger <davidm@hpl.hp.com>,
linux-ia64@linuxia64.org, <guile-devel@gnu.org>
Subject: Re: Guile garbage collector on ia64-linux
Date: Wed, 25 Jun 2003 09:58:07 -0700 [thread overview]
Message-ID: <16121.54431.794996.977946@napali.hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306250438590.251-100000@bono.reversers.net>
>>>>> On Wed, 25 Jun 2003 04:58:59 +0200 (CEST), stefan <stefan@lkcc.org> said:
Stefan> * have some header where ucontext_t is declared but
Stefan> setcontext()/getcontext() is not -> so we can redeclare it
Stefan> to make getcontext() return the 'struct rv'.
One way of achieving this is to do:
#define getcontext hide_getcontext
#include <ucontext.h>
#undef getcontext
Andreas suggested another method. Both have their ups and downs.
Stefan> * determination of the size and location of the backing
Stefan> store; this has been previously achieved by:
Stefan> ctx.uc_mcontext.sc_ar_bsp -> the top
Stefan> __libc_ia64_register_backing_store_base -> the bottom Newer
Stefan> glibc headers don't have 'sc_ar_bsp', but things like
Stefan> 'ar_bsp_base' or 'ar_bspstore'. Can something in the
Stefan> structure ucontext_t be used to achieve the same? Will this
Stefan> change often in the future?
This doesn't sound right. There were no member-name changes "struct
sigcontext". I just checked the current libc CVS tree and it has:
struct sigcontext
{
:
unsigned long int sc_ar_bsp; /* backing store pointer */
So I don't know why this isn't working for you. What distro are you
using?
--david
next prev parent reply other threads:[~2003-06-25 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15307.10445.674412.197780@napali.hpl.hp.com>
2003-06-25 2:58 ` Guile garbage collector on ia64-linux stefan
2003-06-25 9:34 ` [Linux-ia64] " Andreas Schwab
2003-06-25 16:58 ` David Mosberger [this message]
2003-06-25 18:03 ` stefan
2003-06-25 18:07 ` stefan
2003-09-12 15:35 ` Marius Vollmer
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=16121.54431.794996.977946@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=guile-devel@gnu.org \
--cc=linux-ia64@linuxia64.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).