This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Dealing with warnings & pragma GCC diagnostic in LTO-enabled builds
- From: Emmanuel Blot <eblot dot ml at gmail dot com>
- To: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- Cc: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Wed, 21 May 2014 19:28:32 +0200
- Subject: Re: Dealing with warnings & pragma GCC diagnostic in LTO-enabled builds
- Authentication-results: sourceware.org; auth=none
- References: <CAKJJEPxTBpsd=CGG4ytigoYUrGqCZy-JNv4quRv_GHSsbOxLAg at mail dot gmail dot com> <CAESRpQCoO6y3SkoCNiy3cPJaYT8U-J4TPqPWsviDWU+sUikMdA at mail dot gmail dot com>
Hi Manuel,
> I wonder why the diagnostics are not simply disabled during LTO. Do
> you mean that if you don't use the pragmas you get the warnings twice?
They are not disabled during LTO because those are only triggered at
"link" stage. I do not know about the GCC intrinsics, but I guess some
of the issues may only be detected at this stage.
I have no idea, however, about how to get the info about which stage
generates which kind of warnings. So for now, the same warning list is
provided to both the "compiler" (GIMPLE generation) and the "linker"
(binary generation).
I never observed the same warning to occur twice.
Cheers,
Manu