public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/17404] New: atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7?
@ 2014-09-17 14:05 triegel at redhat dot com
2014-09-17 14:06 ` [Bug libc/17404] " triegel at redhat dot com
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: triegel at redhat dot com @ 2014-09-17 14:05 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=17404
Bug ID: 17404
Summary: atomic_exchange_rel lacking a barrier on MIPS16, GCC
before 4.7?
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: triegel at redhat dot com
CC: drepper.fsp at gmail dot com
MIPS16 on GCC before 4.7 implements atomic_exchange_acq using
__sync_lock_test_and_set (which has only acquire semantics) yet does not define
atomic_exchange_rel. This will lead to atomic_exchange_rel having only acquire
semantics and not release semantics.
__sync_lock_test_and_set might be stronger on MIPS16, but Joseph reports that
he did not see anything special there to give a stronger barrier.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libc/17404] atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7?
2014-09-17 14:05 [Bug libc/17404] New: atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7? triegel at redhat dot com
@ 2014-09-17 14:06 ` triegel at redhat dot com
2015-10-27 23:49 ` jsm28 at gcc dot gnu.org
2015-10-27 23:49 ` cvs-commit at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: triegel at redhat dot com @ 2014-09-17 14:06 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=17404
Torvald Riegel <triegel at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joseph at codesourcery dot com
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libc/17404] atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7?
2014-09-17 14:05 [Bug libc/17404] New: atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7? triegel at redhat dot com
2014-09-17 14:06 ` [Bug libc/17404] " triegel at redhat dot com
@ 2015-10-27 23:49 ` jsm28 at gcc dot gnu.org
2015-10-27 23:49 ` cvs-commit at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: jsm28 at gcc dot gnu.org @ 2015-10-27 23:49 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=17404
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |2.23
--- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
Fixed for 2.23 by requiring GCC >= 4.7 to build glibc and removing the code in
question as dead.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug libc/17404] atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7?
2014-09-17 14:05 [Bug libc/17404] New: atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7? triegel at redhat dot com
2014-09-17 14:06 ` [Bug libc/17404] " triegel at redhat dot com
2015-10-27 23:49 ` jsm28 at gcc dot gnu.org
@ 2015-10-27 23:49 ` cvs-commit at gcc dot gnu.org
2 siblings, 0 replies; 4+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2015-10-27 23:49 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=17404
--- Comment #1 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, master has been updated
via 8f82f28bbaa6ca503e6296b2d26ecf213bceff88 (commit)
from f1d237df1eec1df8cbc34f95540fd4035776e79c (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=8f82f28bbaa6ca503e6296b2d26ecf213bceff88
commit 8f82f28bbaa6ca503e6296b2d26ecf213bceff88
Author: Joseph Myers <joseph@codesourcery.com>
Date: Tue Oct 27 23:47:56 2015 +0000
Remove MIPS16 atomics using __sync_* (bug 17404).
MIPS16 atomics used __sync_* with GCC before 4.7, which as noted in
bug 17404 is missing the required barrier semantics for
atomic_exchange_rel. This patch removes the code in question as dead
now GCC before 4.7 is no longer supported for building glibc.
Sanity tested with builds for MIPS.
[BZ #17404]
* sysdeps/mips/atomic-machine.h
[__GNUC_PREREQ (4, 8) || (__mips16 && __GNUC_PREREQ (4, 7))]:
Change conditional to [__GNUC_PREREQ (4, 8) || __mips16].
[__mips16 && !__GNUC_PREREQ (4, 7)]: Remove conditional code.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 6 ++++++
NEWS | 20 ++++++++++----------
sysdeps/mips/atomic-machine.h | 27 +--------------------------
3 files changed, 17 insertions(+), 36 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-10-27 23:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-09-17 14:05 [Bug libc/17404] New: atomic_exchange_rel lacking a barrier on MIPS16, GCC before 4.7? triegel at redhat dot com
2014-09-17 14:06 ` [Bug libc/17404] " triegel at redhat dot com
2015-10-27 23:49 ` jsm28 at gcc dot gnu.org
2015-10-27 23:49 ` cvs-commit at gcc dot gnu.org
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).