From: Steve Tynor <tynor@atlanta.twr.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] setjmp/longjmp and/or *context() routines for IA64?
Date: Wed, 25 Oct 2000 19:35:39 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205629@msgid-missing> (raw)
A few weeks ago, David Mosberger responded to my request for a setjmp
implementation that I could use for doing user-mode context switches.
He said that there were pending changes to setjmp that might help:
| (2) The current setjmp()/longjmp() implementation cannot be used for
| stack switching purposes, because it does not preserve ar.rnat.
| There was some discussion on what we should do about this and the
| conclusion was to fix the routines so they do preserve ar.rnat.
| The main argument for changing the routines was that the IA-64
| SCRA requires ar.rnat to be part of the jmp_buf.
And further,
| (4) If the app absolutely must implement its own thread packages, use
| the *context() routines defined by the Single UNIX Spec. The
| only trouble is that they haven't been implemented for Linux yet.
| (Anyone volunteers?)
I've cvs up'd the latest glibc from http://sources.redhat.com/glibc/ and
all I see is version 2.1.95. Are there relevant changes on the 2.2
branch? If so, how do I go about getting access to the latest and
greatest? Even if I can't use the glibc setjmp directly, I'm hoping I
can adapt it or something like it to what I need. Seeing the diffs
David mentions in #2 above might help me better understand how the
voodoo works.
Thanks!
Steve
next reply other threads:[~2000-10-25 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 19:35 Steve Tynor [this message]
2000-10-25 19:43 ` [Linux-ia64] setjmp/longjmp and/or *context() routines for IA64? Jes Sorensen
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-105590678205629@msgid-missing \
--to=tynor@atlanta.twr.com \
--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