public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/57370] New: [4.9 Regression] compile time hog in reassoc
Date: Wed, 22 May 2013 14:18:00 -0000	[thread overview]
Message-ID: <bug-57370-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57370
           Summary: [4.9 Regression] compile time hog in reassoc
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Joost.VandeVondele at mat dot ethz.ch

Between rev 199047 and 199075 the attached testcase started using an excessive
amount of time (up from about 4s with 4.7.2). The important option seems to be
-ffast-math (16s without this option).

Reproduce with:

time gfortran -c -g -O2 -ffast-math bug.f90

The stack looks like:

#0  0x0000000000af4b79 in reassociate_bb(basic_block_def*) ()
#1  0x0000000000af4ae8 in reassociate_bb(basic_block_def*) ()
#2  0x0000000000af4ae8 in reassociate_bb(basic_block_def*) ()
#3  0x0000000000af4ae8 in reassociate_bb(basic_block_def*) ()
#4  0x0000000000af4ae8 in reassociate_bb(basic_block_def*) ()
#5  0x0000000000af6701 in execute_reassoc() ()
#6  0x0000000000906550 in execute_one_pass(opt_pass*) ()


             reply	other threads:[~2013-05-22 14:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 14:18 Joost.VandeVondele at mat dot ethz.ch [this message]
2013-05-22 14:18 ` [Bug middle-end/57370] " Joost.VandeVondele at mat dot ethz.ch
2013-05-22 14:19 ` Joost.VandeVondele at mat dot ethz.ch
2013-05-22 14:28 ` rguenth at gcc dot gnu.org
2013-05-22 14:32 ` Joost.VandeVondele at mat dot ethz.ch
2013-05-23  6:14 ` Joost.VandeVondele at mat dot ethz.ch
2013-05-24  6:36 ` [Bug middle-end/57370] [4.9 Regression] compiler hangs " Joost.VandeVondele at mat dot ethz.ch
2013-06-05 11:19 ` Joost.VandeVondele at mat dot ethz.ch
2013-06-13  6:04 ` Joost.VandeVondele at mat dot ethz.ch
2013-06-13  7:43 ` [Bug tree-optimization/57370] " glisse at gcc dot gnu.org
2013-08-20 18:32 ` Joost.VandeVondele at mat dot ethz.ch
2013-09-04 17:48 ` eraman at gcc dot gnu.org
2013-09-14  9:02 ` Joost.VandeVondele at mat dot ethz.ch

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-57370-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).