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 debug/64817] New: compilation hangs at -O3 with -g enabled on x86_64-linux-gnu
Date: Tue, 27 Jan 2015 07:04:00 -0000	[thread overview]
Message-ID: <bug-64817-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64817

            Bug ID: 64817
           Summary: compilation hangs at -O3 with -g enabled on
                    x86_64-linux-gnu
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: su at cs dot ucdavis.edu

The following code causes the current gcc trunk to hang at -O3 with -g enabled. 

This is a regression from 4.9.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/5.0.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 5.0.0 20150126 (experimental) [trunk revision 220102] (GCC) 
$ 
$ gcc-trunk -O3 -c small.c
$ gcc-trunk -O2 -g -c small.c
$ gcc-4.9 -O3 -g -c small.c
$ 
$ timeout -s 9 30 gcc-trunk -O3 -g -c small.c
Killed
$ 


------------------------------


int a, b, d;

void
fn1 ()
{
  for (b = 0; b < 9; b++)
    {
      int e;
      for (d = 0; d < 5; d++)
    {
      a &= 231;
      a ^= 14;
    }
      e = (a ^= 1) < 0;
    }
}


             reply	other threads:[~2015-01-27  7:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  7:04 su at cs dot ucdavis.edu [this message]
2015-01-27  8:56 ` [Bug debug/64817] [5 Regression] " jakub at gcc dot gnu.org
2015-01-27 11:10 ` rguenth at gcc dot gnu.org
2015-01-27 12:02 ` jakub at gcc dot gnu.org
2015-01-30 10:10 ` jakub at gcc dot gnu.org
2015-01-30 12:51 ` jakub at gcc dot gnu.org
2015-02-01 17:26 ` jakub at gcc dot gnu.org
2015-02-01 22:02 ` jakub at gcc dot gnu.org
2015-02-04 14:24 ` aoliva at gcc dot gnu.org
2015-02-04 14:24 ` aoliva at gcc dot gnu.org
2015-02-06 11:37 ` 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-64817-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).