From: Progyan Bhattacharya <bprogyan@gmail.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Use of GCC plugin instead ISO C
Date: Sun, 18 Feb 2018 13:36:58 +0530 [thread overview]
Message-ID: <1518941218.12663.1.camel@gmail.com> (raw)
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.
Flags I found being used in compilation so far,
tools/objtool/Makefile:
-Wall -Werror -Wno-switch-default -Wno-switch-enum -Wno-packed
tools/scripts/Makefile.include:
-Wbad-function-cast -Wdeclaration-after-statement -Wformat-
security -Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-
prototypes -Wnested-externs -Wno-system-headers -Wold-style-definition
-Wpacked -Wredundant-decls -Wshadow -Wstrict-prototypes -Wswitch-
default -Wswitch-enum -Wundef -Wwrite-strings -Wformat
Compiler I am using:
gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC)
Thanks in advance.
--
Regards,
Progyan Bhattacharya
(http://codeprogyan.me)
next reply other threads:[~2018-02-18 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 8:06 Progyan Bhattacharya [this message]
2018-02-18 16:47 ` Use of GCC plugin instead ISO C Randy Dunlap
2018-02-22 14:37 ` Progyan Bhattacharya
2018-03-01 7:50 ` Re[v2]: " Progyan Bhattacharya
2018-03-01 21:42 ` Randy Dunlap
2018-03-06 13:28 ` Progyan Bhattacharya
2018-03-06 17:24 ` Randy Dunlap
2018-03-07 6:01 ` Progyan Bhattacharya
2018-03-07 17:36 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1518941218.12663.1.camel@gmail.com \
--to=bprogyan@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.