This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/67002] [5] [SH]: Bootstrap stage 2/3 comparison failure - gcc/real.o differs
- From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 30 Jul 2015 09:01:41 +0000
- Subject: [Bug target/67002] [5] [SH]: Bootstrap stage 2/3 comparison failure - gcc/real.o differs
- Auto-submitted: auto-generated
- References: <bug-67002-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67002
--- Comment #10 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Oleg Endo from comment #9)
> Not sure if this is a good idea.
I actually think it is the best option as chances are dim otherwise that we
find what's actually causing this register indeterminacy.
Looking at the build log, it's only gcc/real.o where the comparison fails, all
the others (except for the checksum files) are find. I think chances are that,
if this is actually a real bug, it might show itself more pronounced when we
use gcc-5 to build other packages.
Just look at how many bugs we were able to find in gcc-4.9 while using it as
the standard host compiler on Debian sh4.
You are right that ignoring this failure is most certainly not the best on a
release architecture that people rely on. But currently, Debian on sh4 is
merely just a port and things are expected to break from time to time.
I am currently building now a patched gcc-5_5.2.1-12 which has gcc/real.o added
to compare_exclusions, let's see how far we get.
Adrian