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/59387] New: wrong code (hangs) at -Os on x86_64-linux-gnu Date: Wed, 04 Dec 2013 18:41:00 -0000 [thread overview] Message-ID: <bug-59387-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59387 Bug ID: 59387 Summary: wrong code (hangs) at -Os on x86_64-linux-gnu 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 miscompiles the following code on x86_64-linux at -Os (but not at the other optimization levels) 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 --prefix=/usr/local/gcc-trunk --enable-languages=c,c++ --disable-werror --enable-multilib Thread model: posix gcc version 4.9.0 20131204 (experimental) [trunk revision 205673] (GCC) $ $ gcc-trunk -O1 small.c; a.out $ gcc-trunk -O2 small.c; a.out $ gcc-4.8 -Os small.c; a.out $ $ gcc-trunk -Os small.c $ a.out ^C $ ------------------------- int a, *d, **e = &d, f; char c; struct { int f1; } b; int main () { for (a = -19; a; a++) { for (b.f1 = 0; b.f1 < 24; b.f1++) c--; *e = &f; if (!d) return 0; } return 0; }
next reply other threads:[~2013-12-04 18:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-04 18:41 su at cs dot ucdavis.edu [this message] 2013-12-05 10:57 ` [Bug tree-optimization/59387] " rguenth at gcc dot gnu.org 2013-12-19 11:01 ` [Bug tree-optimization/59387] [4.9 Regression] " jakub at gcc dot gnu.org 2013-12-19 11:22 ` jakub at gcc dot gnu.org 2013-12-19 11:31 ` jakub at gcc dot gnu.org 2014-01-08 16:38 ` jakub at gcc dot gnu.org 2014-01-08 22:48 ` jakub at gcc dot gnu.org 2014-01-09 9:34 ` rguenth at gcc dot gnu.org 2014-01-10 14:56 ` jakub at gcc dot gnu.org 2014-01-13 19:14 ` jakub at gcc dot gnu.org 2014-01-15 21:43 ` law at redhat dot com 2014-01-16 19:15 ` jakub 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-59387-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).