Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: Hilfinger@otisco.mckusick.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Add SYMBOL_SET_LINKAGE_NAME
Date: Wed, 18 Feb 2004 16:45:00 -0000	[thread overview]
Message-ID: <yf2u11o49qr.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <200402180811.i1I8BnC11365@otisco.McKusick.COM> (Paul N. Hilfinger's message of "Wed, 18 Feb 2004 00:11:49 -0800")

On Wed, 18 Feb 2004 00:11:49 -0800, "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com> said:

> I admit that I have never been clear on the precise limits of
> "linkage name".  The linker DOES see these things (else how do they
> find their way into the executable file?) although it's true that it
> does not "link" them as it does for regular symbols.

> After watching you struggle manfully through a number of terminology
> changes, I was a little reluctant to suggest the introduction of
> still another concept, so I stuck with "linkage name".  The point is
> that WHATEVER you call Ada's mangled type names, they are NOT what
> is written in the source code (so can't be "natural names") and they
> ARE the raw names extracted from the executable's debugging
> information.  Hmm; they also happen to be what I proposed calling
> "search names"---i.e., the names used internally to search by.  We
> could use the opportunity to introduce search names and make this
> "SET_SEARCH_NAME".  Just a thought.

I was actually having similar thoughts on the way into work this
morning.  Maybe what I should focus on first is trying to establish
the notion that, when calling lookup_symbol, the name you pass in
always has to be in the appropriate form: in particular, lookup_symbol
would never try to demangle a name on the fly.  In the non-Ada world,
that would mean that we always search by natural name; but it would
pave the way for you to introduce your SYMBOL_SEARCH_NAME concept.
That way, SYMBOL_SEARCH_NAME would have a clear meaning (even if
nothing else would :-) ): it would be the name that you pass to
lookup_symbol when trying to search for that symbol.

Does that make sense to you?  If so, I'll start generating appropriate
patches.

David Carlton
carlton@kealia.com


  reply	other threads:[~2004-02-18 16:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 21:24 Daniel Jacobowitz
2004-02-16 21:53 ` Elena Zannoni
2004-02-16 22:57   ` Daniel Jacobowitz
2004-02-16 23:35     ` Paul Hilfinger
2004-02-17  0:05       ` Daniel Jacobowitz
2004-02-17  9:59         ` Paul N. Hilfinger
2004-02-17 15:57     ` Andrew Cagney
2004-02-17 16:01       ` Daniel Jacobowitz
2004-02-17 19:14         ` Elena Zannoni
2004-02-17 19:29           ` Daniel Jacobowitz
2004-02-17 23:10             ` Andrew Cagney
2004-02-18  0:43             ` Elena Zannoni
2004-02-18  1:04               ` Daniel Jacobowitz
2004-02-18  0:20 ` David Carlton
2004-02-18  0:23   ` Daniel Jacobowitz
2004-02-18  0:27     ` Elena Zannoni
2004-02-18  0:32       ` Daniel Jacobowitz
2004-02-18  0:54         ` Elena Zannoni
2004-02-18  1:06           ` Daniel Jacobowitz
2004-02-18  0:49   ` Paul Hilfinger
2004-02-18  1:27     ` David Carlton
2004-02-18  8:12       ` Paul N. Hilfinger
2004-02-18 16:45         ` David Carlton [this message]
2004-02-20  9:32           ` Paul N. Hilfinger

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=yf2u11o49qr.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=Hilfinger@otisco.mckusick.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