public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Tom Horsley <Tom.Horsley@mail.ccur.com>
Cc: gcc@gnu.org
Subject: Re: C++ ABI?
Date: Mon, 19 Aug 2002 10:15:00 -0000	[thread overview]
Message-ID: <u8n0rilqh0.fsf@gromit.moeb> (raw)
In-Reply-To: <20020819162852.GA10931@nevyn.them.org>

Daniel Jacobowitz <drow@mvista.com> writes:

> On Mon, Aug 19, 2002 at 04:24:48PM +0000, Tom Horsley wrote:
>> OK, I give up! The gcc 3.2 release trumpets its compatibility with the
>> so-called C++ ABI, yet the http://gcc.gnu.org/gcc-3.2/c++-abi.html web page
>> says ABSOLUTELY NOTHING about what the C++ ABI is, who defined it, where to
>> get a copy of it, how to read about it, etc.
>> 
>> I have never managed to turn up anything in any web search for this mythical
>> document other than references to its existance. The document itself seems
>> to be shrouded in absolute secrecy.
>> 
>> Help! Can anyone point me to this thing? Thanks.
>
> That page does need a link to it.

Please send a patch for the page,

> gcc.gnu.org -> Further Readings -> The V3 multi-vendor standard ABI
>   http://www.codesourcery.com/cxx-abi/

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2002-08-19 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19  9:25 Tom Horsley
2002-08-19  9:26 ` David Edelsohn
2002-08-19  9:28 ` Daniel Jacobowitz
2002-08-19 10:15   ` Andreas Jaeger [this message]
2002-09-11  7:33     ` PATCH for " Gerald Pfeifer
2002-08-19  9:46 Horsley Tom
2002-08-19  9:47 ` David S. Miller
2002-08-19 10:34 ` Phil Edwards

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=u8n0rilqh0.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=Tom.Horsley@mail.ccur.com \
    --cc=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).