public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/58570] New: wrong code at -Os and above on x86_64-linux-gnu (both 32-bit and 64-bit modes) Date: Sat, 28 Sep 2013 20:53:00 -0000 [thread overview] Message-ID: <bug-58570-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58570 Bug ID: 58570 Summary: wrong code at -Os and above on x86_64-linux-gnu (both 32-bit and 64-bit modes) Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: su at cs dot ucdavis.edu The current gcc trunk mis-compiles the following code on x86_64-linux at -Os and above in both 32-bit and 64-bit modes. This is a regression from 4.8.x. $ gcc-trunk -v Using built-in specs. COLLECT_GCC=gcc-trunk COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../gcc-trunk/configure --enable-languages=c,c++,objc,obj-c++,fortran,lto --disable-werror --enable-checking=release --with-gmp=/usr/local/gcc-trunk --with-mpfr=/usr/local/gcc-trunk --with-mpc=/usr/local/gcc-trunk --with-cloog=/usr/local/gcc-trunk --prefix=/usr/local/gcc-trunk Thread model: posix gcc version 4.9.0 20130928 (experimental) [trunk revision 203003] (GCC) $ $ gcc-trunk -O1 small.c $ a.out 1 $ gcc-4.8 -O3 small.c $ a.out 1 $ gcc-trunk -O3 small.c $ a.out 0 $ gcc-trunk -O2 small.c $ a.out 0 $ gcc-trunk -Os small.c $ a.out 0 $ ------------------------------------ int printf (const char *, ...); #pragma pack(1) struct S { int f0:15; int f1:29; }; int a, b, c, e = 1, g; static struct S d[6]; long long f; static short foo (int p) { for (b = 0; b < 1; b++) { g |= 1; for (; a < 1; a++) { int i; if (p < c - 1) return 4; if (p) for (i = 0; i < 6; i++) { struct S j = {1, 1}; d[i] = j; } continue; } } return 0; } int main () { if (e) foo (!f); printf ("%d\n", d[0].f1); return 0; }
next reply other threads:[~2013-09-28 20:53 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-28 20:53 su at cs dot ucdavis.edu [this message] 2013-09-30 10:15 ` [Bug tree-optimization/58570] [4.9 Regression] " rguenth at gcc dot gnu.org 2013-10-06 7:07 ` bernd.edlinger at hotmail dot de 2013-10-06 10:48 ` bernd.edlinger at hotmail dot de 2013-10-06 15:08 ` mikpelinux at gmail dot com 2013-10-07 21:07 ` ebotcazou at gcc dot gnu.org 2013-10-07 21:13 ` [Bug tree-optimization/58570] [4.9 Regression] wrong code for bitfields at -O2 and above ebotcazou at gcc dot gnu.org 2013-10-08 6:47 ` bernd.edlinger at hotmail dot de 2013-10-08 8:07 ` ebotcazou at gcc dot gnu.org 2013-10-08 8:09 ` [Bug middle-end/58570] " ebotcazou at gcc dot gnu.org 2013-10-08 17:43 ` bernd.edlinger at hotmail dot de 2013-10-08 17:56 ` ebotcazou at gcc dot gnu.org 2013-10-08 18:21 ` bernd.edlinger at hotmail dot de 2013-10-09 12:59 ` ebotcazou at gcc dot gnu.org 2013-10-09 13:10 ` ebotcazou at gcc dot gnu.org 2013-10-10 12:02 ` rguenth 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-58570-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).