public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhazeghi at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/57359] New: wrong code for union access at -O3 on x86_64-linux Date: Tue, 21 May 2013 18:20:00 -0000 [thread overview] Message-ID: <bug-57359-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57359 Bug ID: 57359 Summary: wrong code for union access at -O3 on x86_64-linux Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: dhazeghi at yahoo dot com The following code is miscompiled with current gcc 4.8 branch and trunk at -O3 on x86_64-linux. The last write to the union appears to be getting removed (*k = 0), so that the program outputs '1' instead of '0'. This behavior does not occur on 4.7. $ gcc-trunk -v gcc version 4.9.0 20130521 (experimental) [trunk revision 199148] (GCC) $ gcc-trunk -O2 wrong.c $ ./a.out 0 $ gcc-4.7 -O3 wrong.c $ ./a.out 0 $ gcc-trunk -O3 wrong.c $ ./a.out 1 $ ------------------------------- int printf(const char *, ...); union { int i; long long ll; } u; unsigned int i; int a; int *pa = &a; int **ppa = &pa; int ia[1][1]; long long *la[][1][1] = { {}, {}, {}, {}, 0, &u.ll }; long long **ppll = &la[4][1][0]; long long ll = 1; void foo () { for (; i <= 1; i++) { int *j; int *k = &u.i; **ppll = ll; *k = 0; j = *ppa; ia[0][0] = *j; } } int main () { foo (); printf ("%d\n", u.i); return 0; }
next reply other threads:[~2013-05-21 18:20 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-21 18:20 dhazeghi at yahoo dot com [this message] 2013-05-21 18:26 ` [Bug rtl-optimization/57359] " pinskia at gcc dot gnu.org 2013-05-21 18:33 ` jakub at gcc dot gnu.org 2013-05-23 19:51 ` dhazeghi at yahoo dot com 2013-05-29 21:14 ` dhazeghi at yahoo dot com 2013-05-30 7:13 ` jakub at gcc dot gnu.org 2013-05-31 8:48 ` rguenth at gcc dot gnu.org 2013-05-31 16:32 ` dhazeghi at yahoo dot com 2013-05-31 21:07 ` joseph at codesourcery dot com 2013-06-03 19:15 ` dhazeghi at yahoo dot com 2013-06-04 12:37 ` [Bug tree-optimization/57359] " rguenth at gcc dot gnu.org 2020-04-20 7:15 ` [Bug tree-optimization/57359] store motion causes wrong code for union access at -O3 rguenth at gcc dot gnu.org 2020-04-20 8:57 ` rguenth at gcc dot gnu.org 2020-04-20 10:50 ` rguenth at gcc dot gnu.org 2020-04-20 12:03 ` rguenth at gcc dot gnu.org 2020-04-20 12:34 ` pascal_cuoq at hotmail dot com 2020-04-20 12:39 ` rguenther at suse dot de 2020-04-21 7:22 ` rguenth at gcc dot gnu.org 2020-04-27 9:17 ` rguenth at gcc dot gnu.org 2020-04-27 9:35 ` rguenth at gcc dot gnu.org 2020-04-27 12:48 ` rguenth at gcc dot gnu.org 2020-04-30 12:25 ` rguenth at gcc dot gnu.org 2020-05-07 10:12 ` cvs-commit at gcc dot gnu.org 2020-05-07 10:13 ` rguenth at gcc dot gnu.org 2020-05-11 12:56 ` rguenth at gcc dot gnu.org 2020-05-11 12:56 ` rguenth at gcc dot gnu.org 2020-05-11 14:53 ` rguenth at gcc dot gnu.org 2020-05-11 14:57 ` rguenth at gcc dot gnu.org 2020-05-12 6:26 ` rguenth at gcc dot gnu.org 2020-05-12 11:53 ` ro at gcc dot gnu.org 2020-05-12 12:13 ` rguenth at gcc dot gnu.org 2020-05-18 9:50 ` rguenth at gcc dot gnu.org 2020-06-11 15:55 ` pinskia at gcc dot gnu.org
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-57359-4@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).