From: "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com>
To: drow@mvista.com
Cc: carlton@bactrian.org, gdb@sources.redhat.com,
ezannoni@redhat.com, jimb@redhat.com
Subject: Re: [rfc] lookups with natural/linkage names
Date: Mon, 26 May 2003 10:43:00 -0000 [thread overview]
Message-ID: <200305261042.h4QAgxc07019@otisco.McKusick.COM> (raw)
In-Reply-To: <20030524143554.GA14905@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 24 May 2003 10:35:55 -0400)
> > 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?
Not exactly, but actually I am not specifically talking about Ada here.
The equation
linkage name == minsym name
worries me a little. The only alterative names to linkage names are
natural names (I'll ignore print names for now). Therefore, the only
possible kind of mangled name is a minsym name.
Are nested function names ever mangled? We seldom consider nested functions,
because they don't occur in official C/C++, but they do occur in GCC's
extensions (and in Pascal and Ada). On IRIX, using Dwarf-2, nested function
names do NOT appear in the minimal symbols (whereas on Linux, they do).
I hope you see why this makes me slightly nervous.
Now, it is true that Ada mangles more stuff (in particular, type names),
but since we never look up demangled names, this is actually somewhat less
of an issue for us.
Paul Hilfinger
next prev parent reply other threads:[~2003-05-26 10:43 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
2003-05-26 10:43 ` Paul N. Hilfinger [this message]
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=200305261042.h4QAgxc07019@otisco.McKusick.COM \
--to=hilfingr@otisco.mckusick.com \
--cc=Hilfinger@otisco.mckusick.com \
--cc=carlton@bactrian.org \
--cc=drow@mvista.com \
--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).