public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Anatoly Vorobey <mellon@pobox.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Proposal: convert function definitions to prototyped form
Date: Mon, 12 Jun 2000 19:16:00 -0000	[thread overview]
Message-ID: <20000613051645.A13495@happy.checkpoint.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10006121815430.29924-100000@propylaea.anduin.com>

On Mon, Jun 12, 2000 at 06:23:27PM -0700, Daniel Berlin wrote:
> Before my patches to eliminate duplicate dwarf2 info, it said there were
> 120k. 
> So something isn't adding up here. 

How do you eliminate them? The vast majority of types in debug info
are duplicate header file types coming from different source files.
Reducing this should cut the number much more drastically than
from 120k to 80k. I'd say by factor of 8 at the very least. 

My code which reads stabs info says that there are 52276 types (not
trying to remove duplicates) defined
in gdb (not including libbfd, libiberty and libopcodes; including them
gives another 13000 or so) and of them 886 unique type *names*. This
gives a lower bound, obviously, since names may be reused or may denote
different types even coming from the same header due to different defines --
but it's also more useful than the raw number since it doesn't count the
multitude of unnamed automatically generated types which are pointers, 
aliases, forward references, etc.

That would mean around one type name per 400 lines of code. Since almost all
type declarations are in header files which are about 1/10 of all sources
in size, it looks reasonable. 

-- 
Anatoly Vorobey,
mellon@pobox.com http://pobox.com/~mellon/
"Angels can fly because they take themselves lightly" - G.K.Chesterton

  reply	other threads:[~2000-06-12 19:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-02  0:50 Kevin Buettner
2000-06-02  2:42 ` Andrew Cagney
2000-06-03  0:13   ` Kevin Buettner
2000-06-03  0:21   ` Kevin Buettner
2000-06-03  4:52     ` Andrew Cagney
2000-06-02  5:26 ` Mark Kettenis
2000-06-02  8:16   ` Kevin Buettner
2000-06-02 10:44     ` J.T. Conklin
2000-06-03  5:17       ` Andrew Cagney
2000-06-05 11:05         ` J.T. Conklin
2000-06-12 16:30       ` Eric Bachalo
2000-06-12 17:29         ` Andrew Cagney
2000-06-12 18:03           ` Daniel Berlin
2000-06-12 18:15             ` Stan Shebs
2000-06-12 18:23               ` Daniel Berlin
2000-06-12 19:16                 ` Anatoly Vorobey [this message]
2000-06-12 19:42                   ` Daniel Berlin
2000-06-12 18:55         ` Kevin Buettner
2000-06-13  3:34         ` Eli Zaretskii
2000-06-03  4:48 ` Andrew Cagney
2000-06-12 18:10 ` Andrew Cagney
2000-06-12 19:48   ` Kevin Buettner
2000-06-02  8:40 David Taylor
2000-06-02 12:10 ` Kevin Buettner
2000-06-03  3:58   ` Eli Zaretskii
     [not found]     ` <eliz@delorie.com>
2000-06-03 10:50       ` Kevin Buettner
2000-06-03 11:37         ` Eli Zaretskii
2000-06-03 18:18         ` Andrew Cagney
2000-06-03 15:42       ` Kevin Buettner
2000-06-02 13:11 David Taylor

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=20000613051645.A13495@happy.checkpoint.com \
    --to=mellon@pobox.com \
    --cc=dan@cgsoftware.com \
    --cc=gdb@sourceware.cygnus.com \
    /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).