public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: libc-hacker@sources.redhat.com
Subject: [patch] alpha nptl fix
Date: Tue, 10 Jan 2006 00:37:00 -0000	[thread overview]
Message-ID: <20060110003724.GB16111@twiddle.net> (raw)

The following appears to be needed after the recent changes to
this file.


r~


2006-01-09  Richard Henderson  <rth@redhat.com>

	* sysdeps/unix/sysv/linux/alpha/bits/pthreadtypes.h (pthread_mutex_t):
	Name __data structure; use this for __next and __prev.

Index: nptl/sysdeps/unix/sysv/linux/alpha/bits/pthreadtypes.h
===================================================================
RCS file: /cvs/glibc/libc/nptl/sysdeps/unix/sysv/linux/alpha/bits/pthreadtypes.h,v
retrieving revision 1.10
diff -u -p -d -r1.10 pthreadtypes.h
--- nptl/sysdeps/unix/sysv/linux/alpha/bits/pthreadtypes.h	27 Dec 2005 15:08:35 -0000	1.10
+++ nptl/sysdeps/unix/sysv/linux/alpha/bits/pthreadtypes.h	9 Jan 2006 23:06:00 -0000
@@ -47,7 +47,7 @@ typedef union
    type is deliberately not exposed.  */
 typedef union __pthread_mutex_u
 {
-  struct
+  struct __pthread_mutex_s
   {
     int __lock;
     unsigned int __count;
@@ -57,8 +57,8 @@ typedef union __pthread_mutex_u
        binary compatibility.  */
     int __kind;
     int __spins;
-    union __pthread_mutex_u *__next;
-    union __pthread_mutex_u *__prev;
+    struct __pthread_mutex_s *__next;
+    struct __pthread_mutex_s *__prev;
 #define __PTHREAD_MUTEX_HAVE_PREV	1
   } __data;
   char __size[__SIZEOF_PTHREAD_MUTEX_T];

             reply	other threads:[~2006-01-10  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10  0:37 Richard Henderson [this message]
2006-01-10  0:49 ` 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=20060110003724.GB16111@twiddle.net \
    --to=rth@twiddle.net \
    --cc=libc-hacker@sources.redhat.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).