From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Andreas Jaeger <aj@suse.de>
Cc: Tom Horsley <Tom.Horsley@mail.ccur.com>, <gcc@gnu.org>,
<gcc-patches@gcc.gnu.org>
Subject: PATCH for Re: C++ ABI?
Date: Wed, 11 Sep 2002 07:33:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0209111631490.84560-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <u8n0rilqh0.fsf@gromit.moeb>
On Mon, 19 Aug 2002, Andreas Jaeger 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.
> Please send a patch for the page,
It seems nobody has dealt with this yet, so I have committed the patch
below.
Gerald
Index: c++-abi.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/c++-abi.html,v
retrieving revision 1.3
diff -u -3 -p -r1.3 c++-abi.html
--- c++-abi.html 15 Aug 2002 17:28:13 -0000 1.3
+++ c++-abi.html 11 Sep 2002 14:31:44 -0000
@@ -8,7 +8,10 @@
<p>
The main point of the GCC 3.2 release is to have a relatively
- stable and common C++ ABI for GNU/Linux and BSD usage.
+ stable and common C++ ABI for GNU/Linux and BSD usage, following
+ the documentation at
+ <a href="http://www.codesourcery.com/cxx-abi/">http://www.codesourcery.com/cxx-abi/</a>.
+
Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0
and GCC 3.1 releases.</p>
prev parent reply other threads:[~2002-09-11 14:33 UTC|newest]
Thread overview: 5+ 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
2002-09-11 7:33 ` Gerald Pfeifer [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=Pine.BSF.4.44.0209111631490.84560-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=Tom.Horsley@mail.ccur.com \
--cc=aj@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--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).