public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] 2 tiny fixes
Date: Fri, 07 Apr 2006 13:55:00 -0000	[thread overview]
Message-ID: <20060407135539.GI30252@sunsite.mff.cuni.cz> (raw)

Hi!

Sorry for posting 2 unrelated things together:
1) there was a typo in unwind-dw2.c change
2) 2.6.17 kernel defines FUTEX_TID_MASK as 0x3fffffff,
   so NPTL should do the same

2006-04-07  Jakub Jelinek  <jakub@redhat.com>

	* sysdeps/generic/unwind-dw2.c (execute_cfa_program): Fix typo in
	the last change.

	* pthreadP.h (FUTEX_TID_MASK): Sync with kernel.

--- libc/sysdeps/generic/unwind-dw2.c.jj	2006-04-07 12:51:01.000000000 +0200
+++ libc/sysdeps/generic/unwind-dw2.c	2006-04-07 12:56:21.000000000 +0200
@@ -900,7 +900,7 @@ execute_cfa_program (const unsigned char
 	  /* ??? Hardcoded for SPARC register window configuration.
 	     At least do not do anything for archs which explicitly
 	     define a lower register number.  */
-#if DWARF_FRAME_REGISTERS < 32
+#if DWARF_FRAME_REGISTERS >= 32
 	  for (reg = 16; reg < 32; ++reg)
 	    {
 	      fs->regs.reg[reg].how = REG_SAVED_OFFSET;
--- libc/nptl/pthreadP.h.jj	2006-03-28 09:13:36.000000000 +0200
+++ libc/nptl/pthreadP.h	2006-04-07 12:57:21.000000000 +0200
@@ -90,7 +90,7 @@ enum
 /* Bits used in robust mutex implementation.  */
 #define FUTEX_WAITERS		0x80000000
 #define FUTEX_OWNER_DIED	0x40000000
-#define FUTEX_TID_MASK		0x1fffffff
+#define FUTEX_TID_MASK		0x3fffffff
 
 
 /* Internal variables.  */

	Jakub

                 reply	other threads:[~2006-04-07 13:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060407135539.GI30252@sunsite.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=drepper@redhat.com \
    --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).