public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pbrook at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/28547]  New: Large compile time regression with -g
Date: Sun, 30 Jul 2006 22:51:00 -0000	[thread overview]
Message-ID: <bug-28547-6527@http.gcc.gnu.org/bugzilla/> (raw)

The attached code shows a large (between 2x and 10x) increase in compile time
when compiled with -g.
With gcc head "-g -O" -ftime-report says:

 symout                :  14.26 (59%) usr   0.09 (24%) sys  15.35 (59%) wall  
13879 kB (17%) ggc
 variable tracking     :   0.86 ( 4%) usr   0.03 ( 8%) sys   0.89 ( 3%) wall  
28140 kB (34%) ggc

With gcc 4.1 even larger slowdowns are also observable with "-O2 -g" and "-O2
-g -fomit-frrame-pointer". These don't seem to occur with head


-- 
           Summary: Large compile time regression with -g
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: compile-time-hog
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pbrook at gcc dot gnu dot org
GCC target triplet: arm-none-linux-gnueabi


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


             reply	other threads:[~2006-07-30 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 22:51 pbrook at gcc dot gnu dot org [this message]
2006-07-30 22:53 ` [Bug debug/28547] " pbrook at gcc dot gnu dot org
2009-03-31 16:04 ` jsm28 at gcc dot gnu dot org
2009-07-15  7:36 ` steven at gcc dot gnu dot 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-28547-6527@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).