This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Possible gcc 4.8.5 bug about RELOC_HIDE marcro in latest kernel code
- From: Wilco Dijkstra <Wilco dot Dijkstra at arm dot com>
- To: "hejianet at gmail dot com" <hejianet at gmail dot com>
- Cc: nd <nd at arm dot com>, "Andrew dot pinski at cavium dot com" <Andrew dot pinski at cavium dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Thu, 21 Sep 2017 12:56:19 +0000
- Subject: Re: Possible gcc 4.8.5 bug about RELOC_HIDE marcro in latest kernel code
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Wilco dot Dijkstra at arm dot com;
- Nodisclaimer: True
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Hi Justin,
> I tried centos 7.4 gcc 4.8.5-16, which seems to announce to fix this issue.
> And I checked the source code, the patch had been included in.
> But no luck, the bug is still there.
>
> Could you please please any advice to me? eg. Is there any ways to disable such
> reload compilation procedure?
Reload is an intrinsic part of register allocation in GCC, it cannot be disabled.
My advice would be to use GCC7 - there are many more issues in GCC4.8
which you will run into sooner or later. I've done many backports for AArch64 and
generally stopped at GCC6, so please don't consider using anything older.
A recent GCC will also generate MUCH more efficient code for AArch64. The
same is true for GLIBC. So why use something as ancient as GCC4.8???
Wilco