From: y2bismil@engmail.uwaterloo.ca
To: GCC- help <gcc-help@gcc.gnu.org>
Subject: Re: gcc name mangling - resolved
Date: Tue, 21 Oct 2003 15:49:00 -0000 [thread overview]
Message-ID: <1066751376.3f95559055c8e@www.nexusmail.uwaterloo.ca> (raw)
In-Reply-To: <5.2.1.1.0.20031021070608.00b0e160@iplan-mn.corp.adobe.com>
Hi all,
I think I've found the most appropriate solution. Define the functions within
an extern "C" and using the asm 'naming' system.
extern "C"
{
extern void write_char(char) asm("write_char");
}
And if I can remember my old work correctly. They had something like that,
which is why name mangling was not an issue.
Yamin
Quoting Eljay Love-Jensen <eljay@adobe.com>:
> Hi Yamin,
>
> Checkout the -fleading-underscore / -fno-leading-underscore flag.
>
> Note: this is a powerful flag, since it has sweeping effects.
>
> HTH,
> --Eljay
>
>
----------------------------------------
This mail sent through www.mywaterloo.ca
prev parent reply other threads:[~2003-10-21 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 21:29 gcc name mangling y2bismil
2003-10-21 12:06 ` Eljay Love-Jensen
2003-10-21 15:24 ` y2bismil
2003-10-21 15:49 ` y2bismil [this message]
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=1066751376.3f95559055c8e@www.nexusmail.uwaterloo.ca \
--to=y2bismil@engmail.uwaterloo.ca \
--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).