public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40735] memory hog compiling big functions with -fPIE
Date: Tue, 28 Aug 2012 09:34:00 -0000	[thread overview]
Message-ID: <bug-40735-4-pcoet7oUSl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40735-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #19 from Steven Bosscher <steven at gcc dot gnu.org> 2012-08-28 09:34:10 UTC ---
With r190665, compile time is mostly spent in:
 loop doloop             : 130.15 ( 8%) usr
 variable tracking       : 990.72 (60%) usr
 var-tracking dataflow   :  76.34 ( 5%) usr

So this isn't a DF issue in GCC 4.8 at least, but yet another var-tracking
issue (but probably not related to bug 53958, because var-tracking dataflow
time is almost reasonable here).

I'll have a look at the doloop issue, but the var-tracking issue is for Alex.


  parent reply	other threads:[~2012-08-28  9:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40735-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 15:14 ` [Bug target/40735] [4.3/4.4/4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2012-01-16 14:23 ` [Bug target/40735] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-16 14:37 ` [Bug target/40735] " rguenth at gcc dot gnu.org
2012-02-22 13:51 ` xiaoyuanbo at yeah dot net
2012-08-28  8:21 ` steven at gcc dot gnu.org
2012-08-28  8:44 ` steven at gcc dot gnu.org
2012-08-28  8:48 ` amonakov at gcc dot gnu.org
2012-08-28  9:34 ` steven at gcc dot gnu.org [this message]
2012-08-28 10:49 ` steven at gcc dot gnu.org
2012-08-28 11:30 ` steven 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-40735-4-pcoet7oUSl@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).