This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/16549] pthread_cond_wait and pthread_cond_timedwait do not suspend the calling thread
- From: "vinxxe at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 12 Feb 2014 17:25:47 +0000
- Subject: [Bug nptl/16549] pthread_cond_wait and pthread_cond_timedwait do not suspend the calling thread
- Auto-submitted: auto-generated
- References: <bug-16549-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16549
--- Comment #20 from vinxxe at gmail dot com ---
I already agreed with your point. As a matter of fact I removed the bug and
submitted the question to the gcc guys.
(In reply to Rich Felker from comment #18)
> On Wed, Feb 12, 2014 at 10:09:40AM +0000, vinxxe at gmail dot com wrote:
> > seriously, give me a suggestion. I'm only asking for help, no joke!
> > I've searched the web but I didn't find any clear statement about misaligned
> > variables always leading to unpredictable result. I've only found about
> > performance issues. why can't you just give me some reference instead of
> > fooling me?
>
> The C standard simply does not allow misaligned objects to even come
> into existence. The only way you can get them is by performing illegal
> pointer arithmetic/casts/aliasing violations or by using nasty
> nonstandard compiler-specific features like __attribute__ or #pragma
> pack. The latter (these compilers) is where the documentation belongs
> that you cannot take the address of a misaligned object and pass it to
> a function expecting a pointer to that type. At present I don't think
> they are documenting this correctly. This is why I suggested filing a
> bug report against GCC to tag the type so that attempting to pass it
> is a compile-time error.
--
You are receiving this mail because:
You are on the CC list for the bug.