From: stefan <stefan@lkcc.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] use of setcontext()/getcontext()
Date: Sat, 29 Sep 2001 16:53:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805277@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805251@msgid-missing>
On Thu, 27 Sep 2001, David Mosberger wrote:
> struct rv
> {
> long retval;
> long first_return;
> };
>
> int
> swapcontext (ucontext_t *oucp, const ucontext_t *ucp)
> {
> struct rv rv = getcontext (oucp);
> if (rv.first_return)
> setcontext (ucp);
> return 0;
> }
By including <sys/ucontext.h> and declaring getcontext() and setcontext()
by hand it was possible to port the upcoming GNU Guile release 1.6 to
ia64-linux. Thank you very much for your help !
Thanks,
stefan@lkcc.org
next prev parent reply other threads:[~2001-09-29 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 19:35 [Linux-ia64] use of setcontext()/getcontext() stefan
2001-09-26 22:24 ` David Mosberger
2001-09-27 7:31 ` stefan
2001-09-27 17:38 ` David Mosberger
2001-09-29 16:53 ` stefan [this message]
2001-10-09 6:01 ` stefan
2001-10-10 22:17 ` David Mosberger
2001-10-11 11:26 ` stefan
2001-10-11 11:33 ` stefan
2001-10-15 18:16 ` David Mosberger
2001-10-15 18:19 ` David Mosberger
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805277@msgid-missing \
--to=stefan@lkcc.org \
--cc=linux-ia64@vger.kernel.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