public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/52001] New: [4.7 reegression] Huge compile-time regression with var-tracking
Date: Wed, 25 Jan 2012 20:20:00 -0000	[thread overview]
Message-ID: <bug-52001-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52001
           Summary: [4.7 reegression] Huge compile-time regression with
                    var-tracking
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rsandifo@gcc.gnu.org


r182760 significantly increased the compile time of 20001226-1.c -O3 -g
on mips64-linux-gnu:

time for -O3:
    real    0m25.656s
    user    0m25.106s
    sys     0m0.544s

time for -O3 -g before r182760:
    real    0m28.212s
    user    0m27.586s
    sys     0m0.624s

time for -O3 -g after r182760, CTRL-Ced after:
    real    15m11.725s
    user    15m11.177s
    sys     0m0.496s

The testcase has a lot of identical "load high, add low" sequences.
Even though there are only two values here (the high part and
the result), we end up with thousands of value rtxs and thousands
of distinct "reverse" locations attached to the "load high" value.

c.f.: http://gcc.gnu.org/ml/gcc-patches/2012-01/msg01051.html


             reply	other threads:[~2012-01-25 19:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 20:20 rsandifo at gcc dot gnu.org [this message]
2012-01-25 20:23 ` [Bug debug/52001] " pinskia at gcc dot gnu.org
2012-01-25 20:24 ` pinskia at gcc dot gnu.org
2012-01-26 16:13 ` [Bug debug/52001] [4.7 Regression] " jakub at gcc dot gnu.org
2012-01-27 10:07 ` jakub at gcc dot gnu.org
2012-01-27 10:08 ` jakub at gcc dot gnu.org
2012-02-25 12:11 ` aoliva at gcc dot gnu.org
2012-02-25 12:29 ` aoliva at gcc dot gnu.org
2012-02-29 11:36 ` gjl at gcc dot gnu.org
2012-03-01 17:00 ` aoliva 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-52001-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).