From: Joe Buck <Joe.Buck@synopsys.com>
To: jsm28@cam.ac.uk (Joseph S. Myers)
Cc: janis187@us.ibm.com (Janis Johnson), gcc@gcc.gnu.org
Subject: Re: documenting C++ and libstdc++ ABI issues
Date: Tue, 27 Aug 2002 14:52:00 -0000 [thread overview]
Message-ID: <200208272152.OAA29945@atrus.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0208271955520.11231-100000@kern.srcf.societies.cam.ac.uk>
> On Tue, 27 Aug 2002, Janis Johnson wrote:
>
> > This information is of interest to GCC users, not just developers, so
> > it should be in the GCC manual rather than the internals manual.
>
> There's a need for user information about when ABI incompatibilities
> affect linking code built with different compilers or compiler versions.
> But there's also a need for the technical documentation defining what the
> ABI is, where this goes beyond the external standards (e.g., the ABI for
> code using GCC extensions), and what the actual "3.2 ABI" is in cases
> where it differs from the specification (whereas the user documentation
> need only discuss what code is affected, not the detailed differences in
> those cases). I feel that technical documentation fits better in the
> internals manual.
Users will wish to know how to avoid code that tweaks one of the
incompatibilities, and such an explanation could appear in the user
manual. Beyond that, I'd agree that the main guts go in internals.
prev parent reply other threads:[~2002-08-27 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 10:38 Janis Johnson
2002-08-27 11:16 ` Joseph S. Myers
2002-08-27 11:49 ` Janis Johnson
2002-08-27 12:08 ` Joseph S. Myers
2002-08-27 14:52 ` Joe Buck [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=200208272152.OAA29945@atrus.synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=jsm28@cam.ac.uk \
/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).