From: Paul Hilfinger <hilfingr@gnat.com>
To: carlton@kealia.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Proposed changes in symbol-handling for Ada
Date: Wed, 21 Jan 2004 11:22:00 -0000 [thread overview]
Message-ID: <20040121112215.AE278F2810@nile.gnat.com> (raw)
In-Reply-To: <yf2hdyqfcgm.fsf@hawaii.kealia.com> (message from David Carlton on Tue, 20 Jan 2004 15:05:13 -0800)
> 3) Have Ada symbols save the demangled names of symbols after being
> forced to demangle them. This could cause a memory increase if you
> for some reason have to demangle lots of names.
That sounds entirely reasonable.
> (Hmm: where would you allocate the cached name from? You can't get at
> the appropriate obstack from the symbol, can you?
Actually, the only true problem here is that the obvious way of
answering this question---adding to the language-specific union a new
entry containing an obstack* / char* union plus a flag---increases the
size of a symbol (logically it doesn't have to, but C layout and
alignment rules apparently add some padding). To avoid increasing its
size, there is the aesthetically distateful option of adding a flag
byte AFTER the language-specific field; or perhaps we could call it
a union tag. Harumph.
> Sigh. I do not
> enjoy worrying about memory management when programming in C.)
You don't? Good grief, man, what has happened to your sense of
adventure, your thirst for danger?
Paul
next prev parent reply other threads:[~2004-01-21 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 22:55 Interactions of symbol-lookup with language Paul N. Hilfinger
2003-11-10 17:07 ` David Carlton
2004-01-20 10:16 ` [RFC] Proposed changes in symbol-handling for Ada Paul Hilfinger
2004-01-20 15:01 ` Daniel Jacobowitz
2004-01-21 10:55 ` Paul Hilfinger
2004-01-21 15:19 ` Daniel Jacobowitz
2004-01-23 21:08 ` Andrew Cagney
2004-01-20 23:05 ` David Carlton
2004-01-21 11:22 ` Paul Hilfinger [this message]
2004-01-21 16:49 ` David Carlton
2004-01-21 18:50 ` Daniel Jacobowitz
2003-11-11 1:23 ` Interactions of symbol-lookup with language Elena Zannoni
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=20040121112215.AE278F2810@nile.gnat.com \
--to=hilfingr@gnat.com \
--cc=carlton@kealia.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