public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dodji at seketeli dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/33429] debug info for class2 in g++.dg/other/unused1.C  requires -femit-class-debug-always
Date: Fri, 24 Oct 2008 10:58:00 -0000	[thread overview]
Message-ID: <20081024105640.15193.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33429-507@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]



------- Comment #16 from dodji at seketeli dot org  2008-10-24 10:56 -------
Subject: Re:  debug info for class2 in g++.dg/other/unused1.C
  requires -femit-class-debug-always

jason at redhat dot com a écrit :
> Could you (Dodji) try building libstdc++ with -femit-class-debug-always, 
> and see how much it affects the size of the library?

So, I built libstdc++, nemiver, mozilla and openoffice with and without 
the -femit-class-debug-always. I both cases, I did build those programs 
with -g, obviously.

Below are the results of the measurements I did. The debug-info size is 
actually the total size of the elf sections which names are .debug*, 
summed up across all the binaries of a given software.
For a point of comparison, I did also measure the size of .text+data+bss 
segment for both cases.

I hope this helps.

Dodji.

=~=
Nemiver
========
[compact]
debug-info: 43686650
text+data+bss: 13403553

[emit-class-debug-always]
debug-info: 61978858
text+data+bss: 13403793

% increase of debug info size: 42%

libstdc++
=========
[compact]
debug-info: 6474724
text+data+bss: 1282176

[emit-class-debug-always]
debug-info: 6998035
text+data+bss: 1282176

% increase of debug info size: 8%

Mozilla
========
[compact]
debug-info: 882264540
text+data+bss: 60055643

[emit-class-debug-always]
debug-info: 975240699
text+data+bss: 60055739

% increase debug info size: 10,5%

OpenOffice
==========

[compact]
debug-info: 961663753
text+data+bss: 442286732

[emit-class-debug-always]
debug-info: 1010668556
text+data+bss: 442568161

% increase of debug info size: 5%
=~=


-- 


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


      parent reply	other threads:[~2008-10-24 10:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14  6:25 [Bug debug/33429] New: " hp at gcc dot gnu dot org
2007-09-14  6:33 ` [Bug debug/33429] " hp at gcc dot gnu dot org
2007-09-14  6:48 ` hp at gcc dot gnu dot org
2007-09-14 16:33 ` pinskia at gcc dot gnu dot org
2007-09-15 18:39 ` danglin at gcc dot gnu dot org
2007-10-01 15:09 ` rguenth at gcc dot gnu dot org
2008-10-15 18:30 ` jason at gcc dot gnu dot org
2008-10-15 19:38 ` dodji at gcc dot gnu dot org
2008-10-15 20:22 ` mmitchel at gcc dot gnu dot org
2008-10-15 22:24 ` jason at redhat dot com
2008-10-15 22:52 ` mark at codesourcery dot com
2008-10-16 18:41 ` jason at redhat dot com
2008-10-16 20:38 ` mark at codesourcery dot com
2008-10-20 10:21 ` dodji at gcc dot gnu dot org
2008-10-20 19:03 ` jason at redhat dot com
2008-10-20 19:04 ` jason at redhat dot com
2008-10-21 10:16 ` dodji at seketeli dot org
2008-10-24 10:58 ` dodji at seketeli dot org [this message]

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=20081024105640.15193.qmail@sourceware.org \
    --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).