public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vinxxe at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/16549] pthread_cond_wait and pthread_cond_timedwait do not suspend the calling thread
Date: Tue, 11 Feb 2014 18:54:00 -0000 [thread overview]
Message-ID: <bug-16549-131-kBiFqKDnju@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16549-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16549
vinxxe at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |MOVED
--- Comment #8 from vinxxe at gmail dot com ---
I think (In reply to Rich Felker from comment #7)
> BTW I think this general class of bugs should be filed as a bug against GCC:
> misaligned packed structure members should have the fact that they're
> misaligned encoded as part of their type, so that applying the address-of
> operator to them yields a pointer type that's not compatible with the
> standard pointer type. Then,
> pthread_cond_wait(&packed_struct.misaligned_cond, ...) would yield a
> compile-time error due to incompatible pointer types. Likewise, the
> compile's format string warnings could catch the mismatched pointer type in
> scanf("%d", &packed_struct.foo).
I think this is a good point so I'll try to submit this bug to the GCC guys.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-11 18:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 13:28 [Bug nptl/16549] New: " vinxxe at gmail dot com
2014-02-10 13:29 ` [Bug nptl/16549] " vinxxe at gmail dot com
2014-02-10 13:33 ` schwab@linux-m68k.org
2014-02-10 13:38 ` vinxxe at gmail dot com
2014-02-10 13:43 ` neleai at seznam dot cz
2014-02-10 13:45 ` jakub at redhat dot com
2014-02-10 13:46 ` vinxxe at gmail dot com
2014-02-11 17:50 ` bugdal at aerifal dot cx
2014-02-11 17:53 ` bugdal at aerifal dot cx
2014-02-11 18:54 ` vinxxe at gmail dot com [this message]
2014-02-12 9:24 ` vinxxe at gmail dot com
2014-02-12 9:35 ` schwab@linux-m68k.org
2014-02-12 9:43 ` vinxxe at gmail dot com
2014-02-12 9:48 ` jakub at redhat dot com
2014-02-12 9:51 ` vinxxe at gmail dot com
2014-02-12 10:01 ` schwab@linux-m68k.org
2014-02-12 10:09 ` vinxxe at gmail dot com
2014-02-12 10:44 ` schwab@linux-m68k.org
2014-02-12 11:34 ` vinxxe at gmail dot com
2014-02-12 17:10 ` bugdal at aerifal dot cx
2014-02-12 17:18 ` bugdal at aerifal dot cx
2014-02-12 17:25 ` vinxxe at gmail dot com
2014-02-12 17:42 ` vinxxe at gmail dot com
2014-06-13 8:41 ` 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-16549-131-kBiFqKDnju@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).