RE: [PATCH RESEND] gcc-plugins: avoid errors with -std=gnu++11 on old gcc

From: David Laight
Date: Thu Mar 18 2021 - 09:39:38 EST


From: Valdis Kletnieks
> Sent: 18 March 2021 11:56
>
> On Thu, 18 Mar 2021 11:41:29 -0000, David Laight said:
>
> > That gcc bug just implies you need a space after "xxx".
> > That is easily fixable in the sources.
>
> It's not quite that simple.
>
> In file included from /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/tm.h:27,
> from /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/gcc-plugin.h:31,
> from /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/plugin.h:23,
> from scripts/gcc-plugins/gcc-common.h:9,
> from scripts/gcc-plugins/latent_entropy_plugin.c:78:
> >> /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/config/elfos.h:102:21: warning: invalid suffix on
> literal; C++11 requires a space between literal and string macro [-Wliteral-suffix]
> fprintf ((FILE), "%s"HOST_WIDE_INT_PRINT_UNSIGNED"\n",\
>
> The problem isn't in a kernel source file...
...

Could you pass -Wno-literal-suffix on plugin builds?

Might be less faff than changing the -std=xxx' parameter.

David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)