public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/16882] Incorrect implementation of pthread_spin_lock for sparc, no ldstub after spinning
Date: Wed, 04 Jun 2014 00:58:00 -0000 [thread overview]
Message-ID: <bug-16882-131-KCVVTq5IEc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16882-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16882
--- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, release/2.18/master has been updated
via d4deb63367247eaddcbe10b872d39ff70659eaf4 (commit)
from f2b605ed8882a922c403386b2af7e7a5eecbf39f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d4deb63367247eaddcbe10b872d39ff70659eaf4
commit d4deb63367247eaddcbe10b872d39ff70659eaf4
Author: Guo Yixuan <culu.gyx@gmail.com>
Date: Tue Jun 3 16:19:11 2014 -0700
Fixed pthread_spin_lock on sparc32/64 (bug 16882)
[BZ #16882]
* nptl/sysdeps/sparc/sparc32/pthread_spin_lock.S
(pthread_spin_lock): Branch out of spin loop to proper location.
* nptl/sysdeps/sparc/sparc64/pthread_spin_lock.S
(pthread_spin_lock): Likewise.
* nptl/tst-spin4.c: New test.
* nptl/Makefile (tests): Add tst-spin4.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 11 +++
NEWS | 2 +-
nptl/Makefile | 2 +-
nptl/sysdeps/sparc/sparc32/pthread_spin_lock.S | 4 +-
nptl/sysdeps/sparc/sparc64/pthread_spin_lock.S | 4 +-
nptl/tst-spin4.c | 109 ++++++++++++++++++++++++
6 files changed, 126 insertions(+), 6 deletions(-)
create mode 100644 nptl/tst-spin4.c
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-04 0:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 18:39 [Bug nptl/16882] New: " a5b at mail dot ru
2014-05-23 4:33 ` [Bug nptl/16882] " culu.gyx at gmail dot com
2014-05-23 4:33 ` culu.gyx at gmail dot com
2014-05-23 4:36 ` culu.gyx at gmail dot com
2014-05-23 14:26 ` culu.gyx at gmail dot com
2014-05-23 14:34 ` Ondřej Bílka
2014-05-23 14:35 ` neleai at seznam dot cz
2014-05-23 15:09 ` culu.gyx at gmail dot com
2014-05-25 2:12 ` culu.gyx at gmail dot com
2014-05-30 4:38 ` davem at davemloft dot net
2014-06-03 23:11 ` cvs-commit at gcc dot gnu.org
2014-06-03 23:42 ` cvs-commit at gcc dot gnu.org
2014-06-04 0:19 ` cvs-commit at gcc dot gnu.org
2014-06-04 0:58 ` cvs-commit at gcc dot gnu.org [this message]
2014-06-04 1:19 ` cvs-commit at gcc dot gnu.org
2014-06-04 1:22 ` davem at davemloft dot net
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=bug-16882-131-KCVVTq5IEc@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 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).