From: Helge Bahmann <hcb@chaoticmind.net>
To: gcc-help@gcc.gnu.org
Subject: C++ name mangling
Date: Fri, 22 Jul 2005 09:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0507221134390.24601-100000@lothlorien.local> (raw)
Hello,
I would like to create symbol aliases from one symbol to another in an
object file. The way to do it with C symbols "appears" to be:
__asm__(".set foo, bar\n.globl foo\n")
Easy enough; for C++ this works as well, but I have to use the mangled
symbol name. Is there any way to obtain the mangled name of a symbol as
string? The documentation appears to indicate there is none, but I thought
I'd ask nevertheless...
Thanks and best regards
--
Helge Bahmann <hcb@chaoticmind.net> /| \__
The past: Smart users in front of dumb terminals /_|____\
_/\ | __)
$ ./configure \\ \|__/__|
checking whether build environment is sane... yes \\/___/ |
checking for AIX... no (we already did this) |
next reply other threads:[~2005-07-22 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 9:38 Helge Bahmann [this message]
2013-12-13 12:04 Philip Herron
2013-12-13 12:17 ` Jonathan Wakely
2013-12-13 12:40 ` Philip Herron
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=Pine.LNX.4.44.0507221134390.24601-100000@lothlorien.local \
--to=hcb@chaoticmind.net \
--cc=gcc-help@gcc.gnu.org \
/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).