From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Mike Stump <mrs@apple.com>
Cc: Daniel Burrows <dnb114@psu.edu>, <gcc@gnu.org>,
<gcc-patches@gcc.gnu.org>
Subject: Re: PATCH for Re: Broken link on gcc.gnu.org frontpage
Date: Wed, 24 Jul 2002 09:01:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0207240918220.26720-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <BBD6BBA5-9E6A-11D6-84C9-003065A77310@apple.com>
On Tue, 23 Jul 2002, Mike Stump wrote:
> gcc 3.1 has a number of fixes which make it binary incompatible with
> gcc 3.1.
Oops. Fixed thusly.
I also remove "in it" and made it clear that the binaries generated are
incompatible.
Gerald
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/changes.html,v
retrieving revision 1.24
diff -u -3 -p -r1.24 changes.html
--- changes.html 23 Jul 2002 12:52:07 -0000 1.24
+++ changes.html 24 Jul 2002 07:19:13 -0000
@@ -16,9 +16,10 @@
<ul>
<li>This GCC release is based on the GCC 3.1 sourcebase, and thus has
all the <a href="../gcc-3.1/changes.html">changes in the GCC 3.1 series</a>.
- In addition, GCC 3.1 has a number of C++ ABI fixes in it which make its C++
- compiler binary incompatible with the C++ compilers found in earlier GCC
- releases, including GCC 3.1 and GCC 3.1.1.</li>
+ In addition, GCC 3.2 has a number of C++ ABI fixes which make its
+ C++ compiler generate binary code which is incompatible with the C++
+ compilers found in earlier GCC releases, including GCC 3.1 and
+ GCC 3.1.1.</li>
</ul>
prev parent reply other threads:[~2002-07-24 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 16:20 Daniel Burrows
2002-07-23 10:57 ` PATCH for " Gerald Pfeifer
2002-07-23 21:44 ` Mike Stump
2002-07-24 9:01 ` 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.0207240918220.26720-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=dnb114@psu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gnu.org \
--cc=mrs@apple.com \
/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).