Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/types: Clean up use of field bitsize
Date: Wed, 06 Nov 2002 13:52:00 -0000	[thread overview]
Message-ID: <3DC98F36.2030407@redhat.com> (raw)
In-Reply-To: <20021106205431.GA5787@nevyn.them.org>

> On Wed, Nov 06, 2002 at 03:41:10PM -0500, Andrew Cagney wrote:
> 
>> >Does anyone have a comment on this patch?  If not, I'll commit it in a
>> >couple of days, after I'm added to the global write list.
>> >
>> >(The type code has no specific maintainer, the debug reader and
>> >language parts I consider obvious, and the patch is over a month old
>> >now.)
> 
>> 
>> I'm mainly wondering if we're that desperate for memory space.
>> 
>> I thought a data structure was added to GDB so that it could spot 
>> duplicate type info and, hence, keep its memory size down.
> 
> 
> If so, I don't see it.  The debug readers will create a new copy when
> they hit a new definition.

Sigh, looks depressingly like a proposal that fell flat :-(
There are bcache's for macro and psymbol stuff but not types.

> Besides, wasting memory is still bad.  And that's not the reason I did
> it, anyway:

True, the real problem is (true?) the type duplication - gdb is wasting 
memory by duplicating type information - fixing that eliminates the 
problem removing the need for a micro optomization?

Can't find the discussion :-(

>> >>The goal is to allow more kinds of fields to be marked artificial -
>> >>particularly data members.  After this patch I'll submit the followup to
>> >>mark DW_AT_artificial members as artificial types.
> 
> 
> ... in other words, moving artificial out of loc without wasting an
> additional 32 bits.

I'm definitly not questioning this.

Andrew



  reply	other threads:[~2002-11-06 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 18:04 Daniel Jacobowitz
2002-09-29 22:08 ` Paul N. Hilfinger
2002-10-30 15:41 ` Daniel Jacobowitz
2002-11-06 12:41   ` Andrew Cagney
2002-11-06 12:53     ` Daniel Jacobowitz
2002-11-06 13:52       ` Andrew Cagney [this message]
2002-11-10 16:57 ` Daniel Jacobowitz

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=3DC98F36.2030407@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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