public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/13358] R15 may be uninitialized in x86_64/pthread_cond_timedwait.S
Date: Sat, 29 Oct 2011 00:22:00 -0000 [thread overview]
Message-ID: <bug-13358-131-AOB4GGW7KE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13358-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13358
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> 2011-10-29 00:21:54 UTC ---
Whose bright idea was it to write a separate version of these functions for
each target architecture in asm, rather than just using common C code with
underlying asm (or gcc intrinsics) for the atomic memory operations? I'm
thinking of opening a bug "Gratuitous asm leads to arch-specific bugs in
pthread synchronization primitives" so this and similar bugs can all be marked
as a duplicate of it...
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-10-29 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 16:46 [Bug nptl/13358] New: " hjl.tools at gmail dot com
2011-10-28 16:57 ` [Bug nptl/13358] " hjl.tools at gmail dot com
2011-10-29 0:22 ` bugdal at aerifal dot cx [this message]
2011-10-29 19:51 ` drepper.fsp at gmail dot com
2014-06-27 11:42 ` fweimer at redhat dot com
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-13358-131-AOB4GGW7KE@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).