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/61452] New: hang at -O1 and -Os on x86_64-linux-gnu Date: Mon, 09 Jun 2014 00:50:00 -0000 [thread overview] Message-ID: <bug-61452-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61452 Bug ID: 61452 Summary: hang at -O1 and -Os on x86_64-linux-gnu Product: gcc Version: 4.10.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 following (valid) code causes gcc trunk (as well gcc 4.8 and 4.9) to hang at -O1 and -Os (but not at -O0, -O2, and -O3). This is a regression from 4.7.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.10.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.10.0 20140608 (experimental) [trunk revision 211353] (GCC) $ $ gcc-trunk -O0 small.c; a.out $ gcc-trunk -O2 small.c; a.out $ gcc-4.7.3 -O1 small.c; a.out $ gcc-4.7.3 -Os small.c; a.out $ $ timeout -s 9 30 gcc-trunk -O1 small.c Killed $ ---------------------------- int a, b; short c, d; char e, f; int fn1 (int p1, char p2) { return p1 || p2 ? 0 : p2; } void fn2 () { for (; a;) { int g; g = c = e; for (; a;) b = fn1 (g = d = e, g); f = g; } } int main () { fn2 (); return 0; }
next reply other threads:[~2014-06-09 0:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-09 0:50 su at cs dot ucdavis.edu [this message] 2014-06-10 11:15 ` [Bug tree-optimization/61452] [4.8/4.9/4.10 Regression] " rguenth at gcc dot gnu.org 2014-06-11 11:17 ` rguenth at gcc dot gnu.org 2014-06-11 11:18 ` rguenth at gcc dot gnu.org 2014-06-11 11:19 ` [Bug tree-optimization/61452] [4.8 " rguenth at gcc dot gnu.org 2014-09-09 14:46 ` rguenth at gcc dot gnu.org 2014-09-09 14:46 ` 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-61452-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).