public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: prj@po.cwru.edu
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/8146: gcc 3.2 miscompiles gcc 2.95.3
Date: Fri, 04 Oct 2002 10:46:00 -0000 [thread overview]
Message-ID: <20021004174520.29405.qmail@multivac.cwru.edu> (raw)
>Number: 8146
>Category: bootstrap
>Synopsis: gcc 3.2 miscompiles gcc 2.95.3
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Fri Oct 04 10:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Paul Jarc
>Release: 3.2
>Organization:
>Environment:
System: Linux multivac.cwru.edu 2.4.19 #1 SMP Mon Aug 5 11:15:13 EDT 2002 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.2/configure --prefix=/package/host/localhost/gcc-3.2 --with-as=/package/host/localhost/gcc-3.2/conf/as --with-ld=/package/host/localhost/gcc-3.2/conf/ld --enable-threads --enable-libgcj --disable-nls
glibc 2.2.5
binutils 2.13
>Description:
If I start with gcc 3.2 and try to bootstrap gcc 2.95.3, I get
a bootstrap comparison failure. The documentation says that this
usually indicates that the host compiler (gcc 3.2 here) miscompiled
gcc (2.95.3).
Bootstrap comparison failure!
cccp.o differs
f/data.o differs
f/target.o differs
make[1]: *** [compare-lean] Error 1
3.1 and 3.1.1 also fail to bootstrap 2.95.3. IIRC, 3.1 had
differences only in cccp.o.
I suggest adding bootstrapping old versions to the pre-release
testing procedure. Having a buggy compiler is bad; having one
that is buggy in such a way as to complicate downgrading to a
not-known-to-me-to-be-buggy version is worse.
(I was able to downgrade by doing "make install" after the failing
"make bootstrap", and then using that incomplete 2.95.3 to do a
successful bootstrap of a new 2.95.3.)
>How-To-Repeat:
Build 2.95.3 using 3.2. I think you already have the relevant
source files. :) Files from my build or installation
directories of 3.2 or 2.95.3 are available on request.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-10-04 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 10:46 prj [this message]
2002-10-23 16:46 Janis Johnson
2002-10-31 14:16 Joe Buck
2002-11-08 13:56 Joe Buck
2002-11-08 17:06 Joe Buck
2002-12-11 15:46 Richard Henderson
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=20021004174520.29405.qmail@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=gcc-gnats@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).