public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antoine.balestrat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57685] New: GCC stuck in an infinite loop
Date: Sun, 23 Jun 2013 14:25:00 -0000	[thread overview]
Message-ID: <bug-57685-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57685

            Bug ID: 57685
           Summary: GCC stuck in an infinite loop
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: antoine.balestrat at gmail dot com

Hello !
Using GCC 4.9.0 as of 20130623 :

$ cat inf.c
unsigned f(void)
{
    unsigned a;
    int b, c, d, e;

    for(c = 27; c < 40; c++)
        b |= d |= b;

    if(b)
        a = e;

    return a;
}

$ ulimit -t 60

$ xgcc -O3 inf.c
gcc: internal compiler error: CPU time limit exceeded (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


             reply	other threads:[~2013-06-23 14:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23 14:25 antoine.balestrat at gmail dot com [this message]
2013-06-23 15:20 ` [Bug tree-optimization/57685] " mikpe at it dot uu.se
2013-06-23 18:48 ` mikpe at it dot uu.se
2013-06-24 10:49 ` [Bug tree-optimization/57685] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-08-28 13:09 ` rguenth at gcc dot gnu.org
2013-08-29  7:46 ` [Bug tree-optimization/57685] [4.8 " rguenth at gcc dot gnu.org
2013-08-29  7:46 ` [Bug tree-optimization/57685] [4.8/4.9 " rguenth at gcc dot gnu.org
2013-09-09  9:48 ` [Bug tree-optimization/57685] [4.8 " rguenth at gcc dot gnu.org
2013-09-09  9:52 ` 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-57685-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: link
Be 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).