From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jeffrey Turner <jturner@mail.alum.rpi.edu>
Cc: gcc@gcc.gnu.org, <gcc-patches@gcc.gnu.org>
Subject: PATCH for Re: A bug in Chapter 18
Date: Mon, 17 Dec 2001 07:53:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.43.0112171406320.60967-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <200112150847.AA48038212@mail.alum.rpi.edu>
On Sat, 15 Dec 2001, Jeffrey Turner wrote:
> In the first sentence of Chapter 18 - Trees, I believe it should
> read, "This chapter documents the internal representation used by
> GCC and _G_++ [not C++]...."
Thanks for the pointer. Fixed thusly.
(GCC itself is the GNU Compiler Collection, the gcc, g++,... binaries
are all part of GCC itself.)
Gerald
2001-12-17 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* doc/c-tree.texi (Trees): Only refer to GCC.
Index: doc/c-tree.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/c-tree.texi,v
retrieving revision 1.26
diff -u -3 -p -r1.26 c-tree.texi
--- c-tree.texi 2001/12/17 01:18:39 1.26
+++ c-tree.texi 2001/12/17 13:06:21
@@ -12,7 +12,7 @@
@cindex Trees
@cindex C/C++ Internal Representation
-This chapter documents the internal representation used by GCC and C++ to
+This chapter documents the internal representation used by GCC to
represent C and C++ source programs. When presented with a C or C++
source program, GCC parses the program, performs semantic analysis
(including the generation of error messages), and then produces the
prev parent reply other threads:[~2001-12-17 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 5:48 Jeffrey Turner
2001-12-17 7:53 ` 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.43.0112171406320.60967-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jturner@mail.alum.rpi.edu \
/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).