public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Adam Megacz <gcc@lists.megacz.com>
To: gcc@gcc.gnu.org
Subject: mangling of '$'
Date: Tue, 04 Dec 2001 17:16:00 -0000	[thread overview]
Message-ID: <86pu5utqi5.fsf@megacz.com> (raw)


Hi, all. I recently attempted to link code compiled with g++ to code
compiled with gcj. Unfortunately, the link fails because, according to
Bryce McKinlay (who was kind enough to let me quote this):

> Its because gcj and g++ disagree on how the "$" symbol should be 
> mangled. IIRC, the C++ guys agreed that it should do what gcj does 
> (mangle it to a unicode symbol), but they never implemented it.
 
[as discussed in http://gcc.gnu.org/ml/gcc-patches/2001-03/msg01667.html]

Could anybody here please adjust g++'s mangling of "$" to "__U24", as
gcj does? I'd greatly appreciate it.

Also, I know beggars can't be choosers, but since it seems to be a
simple fix, and since it's sort of limiting my ability to proceed, do
you think you could fix it soon? Sorry, I hate to whine like this...

Thanks!

  - a

                 reply	other threads:[~2001-12-05  1:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=86pu5utqi5.fsf@megacz.com \
    --to=gcc@lists.megacz.com \
    --cc=gcc@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).