public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64703] glibc sysdeps/powerpc/powerpc64/dl-machine.h miscompile Date: Wed, 25 Feb 2015 01:06:00 -0000 [thread overview] Message-ID: <bug-64703-4-steaM6cxkI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64703-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64703 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org --- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> --- The test case is invalid because it accesses the value of the opd object via a pointer to a function when C allows an object to have its value accessed only by an lvalue of a compatible type. A simpler test case that demonstrates a similar issue is below: #include <assert.h> struct X { const char *s; }; struct Y { unsigned long n; }; const char* __attribute__ ((weak)) foo (unsigned long value) { struct Y y; if (value) { y.n = ((struct Y*)value)->n; value = (unsigned long)&y; } return ((struct X*)value)->s; } int main (void) { struct Y y = { 123 }; unsigned long n = (unsigned long)foo ((unsigned long)&y); assert (n == y.n); return 0; }
next prev parent reply other threads:[~2015-02-24 23:42 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-21 2:37 [Bug tree-optimization/64703] New: " amodra at gmail dot com 2015-01-21 2:45 ` [Bug tree-optimization/64703] " pinskia at gcc dot gnu.org 2015-01-21 9:03 ` jakub at gcc dot gnu.org 2015-01-21 9:39 ` [Bug target/64703] " rguenth at gcc dot gnu.org 2015-01-21 9:44 ` jakub at gcc dot gnu.org 2015-01-21 9:51 ` schwab@linux-m68k.org 2015-01-21 10:55 ` amodra at gmail dot com 2015-01-23 9:36 ` amodra at gmail dot com 2015-02-25 1:06 ` msebor at gcc dot gnu.org [this message] 2015-03-18 6:39 ` amodra at gmail 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-64703-4-steaM6cxkI@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).