This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/65979] [5/6 Regression] [SH] Wrong code is generated with stage1 compiler
- 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: Wed, 27 May 2015 11:27:23 +0000
- Subject: [Bug target/65979] [5/6 Regression] [SH] Wrong code is generated with stage1 compiler
- Auto-submitted: auto-generated
- References: <bug-65979-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65979
--- Comment #33 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Kazumoto Kojima from comment #32)
> (In reply to John Paul Adrian Glaubitz from comment #28)
> I should have been more clear about these comparison messages.
> Warning is warning and doesn't cause failure. gcc/cc1*-checksum.o
> objects depend on the virtual addresses of executables. If
> randomize-va-space feature of kernel on the target machine is used,
> then stage2/3 cc1*-checksum.o differs without any compiler problem.
> These differences are warned but aren't handled as errors for that reason.
Aha, that would explain that, indeed as it. Checking on two of the buildds:
root@tirpitz:~> cat /proc/sys/kernel/randomize_va_space
2
root@tirpitz:~>
yamashiro:~# cat /proc/sys/kernel/randomize_va_space
2
yamashiro:~#
> It looks that the log for 4.8.4-2 includes
> gcc/d/ctfeexpr.dmd.o differs
> line just after its 'Bootstrap comparison failure!' line. It looks that
> that is the cause of failure and is a differnt issue.
Ah, thanks for spotting that. Now, should we move this into a new bug report
then?
> For the original PR, I've apply the fix on 5/6 in behalf of Oleg after
> the regtest on trunk which has become possible because 66181 is fixed.
Great. Can't wait for the new gcc-5 package to arrive in Debian. Will report
back as soon as I know more.
Adrian