All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>,
	Matthew Wilcox <willy@debian.org>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] new glibc dpatch
Date: Wed, 17 Oct 2001 05:35:49 +0100	[thread overview]
Message-ID: <20011017053549.A22885@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20011017001453.A11826@megatonmonkey.net>; from carlos@megatonmonkey.net on Wed, Oct 17, 2001 at 12:14:53AM -0400

On Wed, Oct 17, 2001 at 12:14:53AM -0400, Carlos O'Donell Jr. wrote:
> Just a comment about your changes to ./sysdeps/ia64/dl-fptr.c
> 
> =====
> --- glibc22-hppa.dpatch	Tue Oct 16 20:52:02 2001
> +++ glibc22-hppa.dpatch.mw	Tue Oct 16 21:05:27 2001
> @@ -1135,7 +1135,7 @@
>       unsigned int npages;		/* # of pages to allocate */
>   #ifdef _LIBC_REENTRANT
>  -    volatile int lock;
> -+    __atomic_lock_t lock;
> ++    static __atomic_lock_t lock = __ATOMIC_LOCK_INIT;
>       sigset_t full_sigset;
>   #endif
>       /* the next to members MUST be consecutive! */
> =====

I'm not sure what meaning static would have in this context.  It doesn't
have to be initialised because every arch other than PA defines an
unlocked lock to be 0.  If it gets initialised, it gets put in .data
(instead of .bss), even if you're initialising it to 0.  Stupid, I know.

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-10-17  4:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 23:42 [parisc-linux] new glibc dpatch Matthew Wilcox
2001-10-17  4:14 ` Carlos O'Donell Jr.
2001-10-17  4:35   ` Matthew Wilcox [this message]
2001-10-17  4:55     ` Carlos O'Donell Jr.

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=20011017053549.A22885@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=carlos@megatonmonkey.net \
    --cc=parisc-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.