Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Add SYMBOL_SET_LINKAGE_NAME
Date: Wed, 18 Feb 2004 01:27:00 -0000	[thread overview]
Message-ID: <yf2y8r141pd.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <200402180049.i1I0n4HR018124@tully.CS.Berkeley.EDU> (Paul Hilfinger's message of "Tue, 17 Feb 2004 16:49:04 -0800")

On Tue, 17 Feb 2004 16:49:04 -0800, Paul Hilfinger <hilfingr@EECS.Berkeley.EDU> said:

>> When we're talking about types, however, linkage names don't make much
>> sense, only natural names.  

> Oh, I DO so hate to rock the boat, but this statement is not true in
> the case of Ada, in which the natural name of a type is not how it's
> known to the linker.

Can you clarify this?  Because:

> I don't see why "linkage names don't make much sense" anyway: the name
> of a (C/C++) type is, indeed, what the linker sees.

I don't see this as being true for C/C++.  The linker sees the names
of functions and variables, but it doesn't see the names of types.
There aren't any minimal symbols associated to types.  There are
minimal symbols associated to methods of classes, static variables of
classes, and other stuff (virtual function tables, at least), but no
minimal symbols associated to the the types themselves.

I can see how you could take the name of a type and mangle it, and I
can imagine that doing so might be useful for Ada (and perhaps even
for C++?), given the picture that you've been painting.  But I
wouldn't call that a linkage name, because there's nothing in the
object file which has that name.

So is the picture different for Ada, or have I not been being clear
with the distinction of linkage name vs. mangled name?  (Or am I
missing something even in the C/C++ case, for that matter?)

David Carlton
carlton@kealia.com


  reply	other threads:[~2004-02-18  1:27 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 [this message]
2004-02-18  8:12       ` Paul N. Hilfinger
2004-02-18 16:45         ` David Carlton
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=yf2y8r141pd.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hilfingr@EECS.Berkeley.EDU \
    /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