public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: libc-hacker@sourceware.cygnus.com
Subject: <sys/ucontext.h> on alpha
Date: Tue, 12 Oct 1999 06:48:00 -0000	[thread overview]
Message-ID: <199910121348.PAA23013@zermelo.suse.de> (raw)

Trying to compile the current glibc 2.2 on alpha, I noticed that
<sys/ucontext.h> isn't in synch with the other architectures.
Appended is a patch to add the missing parts.  I'd appreciate if
somebody would check if this is ok.

Andreas

1999-10-12  Andreas Jaeger  <aj@delta.suse.de>

	* sysdeps/unix/sysv/linux/alpha/sys/ucontext.h: Synch with
	other architectures: Add NGREGS, greg_t, gregset_t, _fpstate.

Index: sysdeps/unix/sysv/linux/alpha/sys/ucontext.h
===================================================================
RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/alpha/sys/ucontext.h,v
retrieving revision 1.2
diff -u -u -r1.2 ucontext.h
--- ucontext.h	1999/03/01 07:20:35	1.2
+++ ucontext.h	1999/10/12 13:46:00
@@ -22,7 +22,21 @@
 #include <features.h>
 #include <signal.h>
 
+/* We need the signal context definitions even if they are not used
+   included in <signal.h>.  */
 #include <bits/sigcontext.h>
+
+/* Type for general register.  */
+typedef long int greg_t;
+
+/* Number of general registers.  */
+#define NGREG	33
+
+/* Container for all general registers.  */
+typedef greg_t gregset_t[NGREG];
+
+/* Structure to describe FPU registers.  */
+typedef struct _fpstate *fpregset_t;
 
 /* A machine context is exactly a sigcontext.  */
 typedef struct sigcontext mcontext_t;

             reply	other threads:[~1999-10-12  6:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-12  6:48 Andreas Jaeger [this message]
1999-10-12  8:52 ` Ulrich Drepper

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=199910121348.PAA23013@zermelo.suse.de \
    --to=aj@suse.de \
    --cc=libc-hacker@sourceware.cygnus.com \
    /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).