From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: libc-hacker@sources.redhat.com
Subject: [PATCH] s390* pthread_spin_unlock.
Date: Fri, 11 Apr 2003 15:46:00 -0000 [thread overview]
Message-ID: <200304111745.37114.schwidefsky@de.ibm.com> (raw)
Hi,
this is one of those "how could this ever work" bugs. The pthread_spin_lock
primitive in linuxthread for s390* is broken. The following patch fixes it.
blue skies,
Martin.
2003-04-11 Martin Schwidefsky <schwidefsky@de.ibm.com>
* sysdeps/s390/pspinlock.c (__pthread_spin_unlock): Fix asm contraints.
diff -urN libc/linuxthreads/sysdeps/s390/pspinlock.c libc-s390/linuxthreads/sysdeps/s390/pspinlock.c
--- libc/linuxthreads/sysdeps/s390/pspinlock.c Fri Apr 11 17:34:17 2003
+++ libc-s390/linuxthreads/sysdeps/s390/pspinlock.c Fri Apr 11 17:33:22 2003
@@ -64,7 +64,7 @@
{
asm volatile(" xc 0(4,%0),0(%0)\n"
" bcr 15,0"
- : "=a" (lock) );
+ : : "a" (lock) : "memory" );
return 0;
}
weak_alias (__pthread_spin_unlock, pthread_spin_unlock)
next reply other threads:[~2003-04-11 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 15:46 Martin Schwidefsky [this message]
2003-04-11 22:06 ` Roland McGrath
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=200304111745.37114.schwidefsky@de.ibm.com \
--to=schwidefsky@de.ibm.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).