public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Damian Minihan <damian.minihan@compans.com>
Cc: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: Re: Clarification
Date: Thu, 06 Jul 2000 04:03:00 -0000	[thread overview]
Message-ID: <oru2e3y0z6.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <5046F7A215B7D211AA4900104B0679A3018D4C3B@newtown.compans.com>

On Jul  6, 2000, Damian Minihan <damian.minihan@compans.com> wrote:

> GNU C++ does not do name mangling in the same way as other C++ compilers.

Correct.  There's no standard C++ ABI as of GCC 2.95.2.  A
cross-platform C++ ABI is currently being specified and developed,
which will allow linking of object files generated by multiple C++
compilers.  Until this work is finished, you'll have to compile all
your C++ code with the same C++ compiler.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

  reply	other threads:[~2000-07-06  4:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-06  3:58 Clarification Damian Minihan
2000-07-06  4:03 ` Alexandre Oliva [this message]
2000-07-06  4:32   ` Clarification Neelakanth
2000-07-06 12:31     ` Clarification Martin v. Loewis
2000-07-06  6:42   ` Clarification Philipp Thomas
  -- strict thread matches above, loose matches on Subject: below --
2001-02-13 13:43 Clarification Sangwan, Vikas (CORP, GEITC)
2001-02-14 17:09 ` Clarification Alexandre Oliva
1999-02-21 15:34 Clarification Jeffrey A Law
1999-02-28 22:53 ` Clarification Jeffrey A Law

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=oru2e3y0z6.fsf@guarana.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=damian.minihan@compans.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).