public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Hilfinger@otisco.mckusick.com
Cc: carlton@bactrian.org, gdb@sources.redhat.com,
	ezannoni@redhat.com, jimb@redhat.com
Subject: Re: [rfc] lookups with natural/linkage names
Date: Sat, 24 May 2003 14:36:00 -0000	[thread overview]
Message-ID: <20030524143554.GA14905@nevyn.them.org> (raw)
In-Reply-To: <200305240811.h4O8BJu10644@otisco.McKusick.COM>

On Sat, May 24, 2003 at 01:11:19AM -0700, Paul N. Hilfinger wrote:
> 
> > * Add a function
> 
> >    struct symbol *lookup_symbol_linkage (const char *name);
> 
> >  that looks up the symbol whose linkage name is NAME.  It only looks
> >  up global or static symbols (with preference to the former), and
> >  only looks up symbols in VAR_DOMAIN; it doesn't apply any
> >  language-specific rules.  This will, for example, give us a reliable
> >  way to find the symbol associated to a minsym, no matter how
> >  complicated C++ lookup rules make things.
> 
> David,
> 
> What exactly is the reasoning that says that such lookups needn't consider
> local (or rather non-static/global) symbols?

Normally, symbols with a linkage name (i.e. that appear in the minsym
table) are only global or static.  Does Ada have an exception to this?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-05-24 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 23:48 David Carlton
2003-05-24  8:11 ` Paul N. Hilfinger
2003-05-24 14:36   ` Daniel Jacobowitz [this message]
2003-05-26 10:43     ` Paul N. Hilfinger
2003-05-27 15:55       ` David Carlton
2003-05-24 21:10   ` David Carlton

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=20030524143554.GA14905@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=Hilfinger@otisco.mckusick.com \
    --cc=carlton@bactrian.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).