public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/54402] [4.8 Regression] var-tracking does not scale
Date: Mon, 29 Oct 2012 17:24:00 -0000	[thread overview]
Message-ID: <bug-54402-4-NbJbNbkifo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54402-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-10-29 17:24:15 UTC ---
Created attachment 28563
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28563
gcc48-pr54402-2.patch

Just for completeness, I'm attaching my earlier attempt to fix the
reflect/check compile time, but unfortunately that only gave speedup from
around 49minutes to 19minutes.  With the huge number of locs values before
gcc48-pr54402.patch
the problem was that find_base_term was extremely expensive, and not cached in
any way.  Once var-tracking finishes initialization, what is find_base_term of
some value shouldn't IMHO change.


  parent reply	other threads:[~2012-10-29 17:24 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  9:48 [Bug debug/54402] New: " steven at gcc dot gnu.org
2012-08-29  9:50 ` [Bug debug/54402] " steven at gcc dot gnu.org
2012-09-03 10:13 ` rguenth at gcc dot gnu.org
2012-10-05 17:57 ` markus at trippelsdorf dot de
2012-10-16 14:42 ` markus at trippelsdorf dot de
2012-10-16 18:38 ` markus at trippelsdorf dot de
2012-10-26 10:53 ` rsandifo at gcc dot gnu.org
2012-10-26 23:07 ` vmakarov at redhat dot com
2012-10-27  7:24 ` ubizjak at gmail dot com
2012-10-29  9:49 ` jakub at gcc dot gnu.org
2012-10-29 17:14 ` jakub at gcc dot gnu.org
2012-10-29 17:24 ` jakub at gcc dot gnu.org [this message]
2012-10-30 10:59 ` markus at trippelsdorf dot de
2012-10-30 11:25 ` markus at trippelsdorf dot de
2012-10-30 12:26 ` markus at trippelsdorf dot de
2012-10-30 18:24 ` jakub at gcc dot gnu.org
2012-11-05  7:59 ` jakub at gcc dot gnu.org
2012-12-06 16:42 ` rguenth at gcc dot gnu.org
2012-12-06 16:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-12-06 17:01 ` jakub at gcc dot gnu.org
2012-12-10 10:57 ` jakub at gcc dot gnu.org
2012-12-12 11:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-12-12 11:10 ` ro at gcc dot gnu.org
2012-12-12 22:10 ` jakub at gcc dot gnu.org
2012-12-12 22:22 ` jakub at gcc dot gnu.org
2012-12-12 22:30 ` jakub at gcc dot gnu.org
2012-12-13 13:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-12-24  0:37 ` jan.smets@alcatel-lucent.com
2013-01-03  8:52 ` jakub at gcc dot gnu.org
2013-01-18 11:01 ` aoliva at gcc dot gnu.org
2013-01-18 11:08 ` aoliva at gcc dot gnu.org
2013-01-21 10:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-01-23 16:49 ` rguenth at gcc dot gnu.org
2013-01-24 12:46 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-03-22 14:43 ` [Bug debug/54402] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:57 ` jakub at gcc dot gnu.org
2013-10-16  9:50 ` jakub at gcc dot gnu.org
2013-10-25 11:20 ` rguenth at gcc dot gnu.org
2013-10-25 11:48 ` 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-54402-4-NbJbNbkifo@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).