linux-kernel - Re: Use of GCC plugin instead ISO C

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7bd655df-39a1-2098-0d1c-256c0900b7ed@infradead.org>
Date:   Sun, 18 Feb 2018 08:47:01 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Progyan Bhattacharya <bprogyan@...il.com>,
        Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Use of GCC plugin instead ISO C

On 02/18/2018 12:06 AM, Progyan Bhattacharya wrote:
> Hi Again,
> 
> According to last time talked, you said me to avoid "-Werror=pedantic"
> flag to build the GNU specific plugins instead of Standard ISO C. I
> changed my default compiler flags and tried to rebuild. But I am still
> getting the same error messages at:
> 
> 	CC /***/Linux/tools/objtool/arch/x86/decode.o
> 
> All of them were arising due to same "-pedantic" flag being enabled.
> 1. Range expression in Case statements were not allowed.
> 2. Use of braced-group were not allowed in MACRO definition.
> 3. Pointer arithmetic with void pointer was not allowed.
> 
> I took a look on related Makefiles, but found none with "-pedantic" or
> "-Werror=pedantic" flag.

I didn't find "pedantic" in any Makefiles either.

You could try (re)building with V=1 on the "make" command line and capture
the output to see where the "pedantic" is coming from.

-- 
~Randy