From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: libc-alpha@sources.redhat.com
Cc: debian-glibc@lists.debian.org, parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] [PATCH] Correctly define mcontext for HPPA
Date: Tue, 19 Nov 2002 01:07:35 -0500 [thread overview]
Message-ID: <20021119060735.GH12451@systemhalted> (raw)
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
libc-alpha,
A machine context is really a signal context.
This has never worked correctly in hppa since the
kernel has always returned a sigcontext instead of
the struct defined in ucontext.h.
This definition change is made such that glibc
matches the ABI, rather than presenting an odd
view of mcontext_t.
The only thought I have...
- Is there enough information in our sigcontext to
implement [set,get,make,swap]context calls?
c.
---
2002-08-20 Carlos O'Donell <carlos@baldric.uwo.ca>
* sysdeps/unix/sysv/linux/hppa/sys/ucontext.h:
Define mcontext_t as a sigcontext.
[-- Attachment #2: 05-glibc23-hppa-mcontext --]
[-- Type: text/plain, Size: 581 bytes --]
diff -urN glibc-2.2.5/sysdeps/unix/sysv/linux/hppa/sys/ucontext.h glibc-2.2.5/sysdeps/unix/sysv/linux/hppa/sys/ucontext.h
--- glibc-2.2.5/sysdeps/unix/sysv/linux/hppa/sys/ucontext.h 2002-08-20 20:50:17.000000000 -0400
+++ glibc-2.2.5/sysdeps/unix/sysv/linux/hppa/sys/ucontext.h 2002-08-20 20:49:01.000000000 -0400
@@ -52,11 +52,7 @@
} fpregset_t;
/* Context to describe whole processor state. */
-typedef struct
- {
- gregset_t gregs;
- fpregset_t fpregs;
- } mcontext_t;
+typedef struct sigcontext mcontext_t;
/* Userlevel context. */
typedef struct ucontext
next reply other threads:[~2002-11-19 6:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 6:07 Carlos O'Donell [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 6:07 [parisc-linux] [PATCH] Correctly define mcontext for HPPA Carlos O'Donell
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=20021119060735.GH12451@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=debian-glibc@lists.debian.org \
--cc=libc-alpha@sources.redhat.com \
--cc=parisc-linux@lists.parisc-linux.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