From: Borislav Petkov <bp@alien8.de>
To: "Jan-Simon Möller" <dl9pf@gmx.de>
Cc: Behan Webster <behanw@converseincode.com>,
Mark Charlebois <mcharleb@gmail.com>,
PaX Team <pageexec@freemail.hu>, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: 3d3d6b847420 ("kbuild: LLVMLinux: Adapt warnings for compilation with clang")
Date: Mon, 16 Jun 2014 15:07:51 +0200 [thread overview]
Message-ID: <20140616130751.GD8170@pd.tnic> (raw)
Hi,
the commit in $Subject breaks the purpose of the W= build to see
additional warnings.
With it, currently I get all that stuff disabled with gcc:
$ make V=1 W=1 fs/direct-io.o
...
gcc -Wp,-MD,... -Wno-sign-compare -Wno-missing-field-initializers
-Wno-unused-value -Wno-format -Wno-sign-compare -Wno-format-zero-length
-Wno-uninitialized ...
which is clearly wrong. If I'm building with W=1, I *explicitly* *want*
those additional warnings enabled, not disabled.
Please fix this to have effect only for clang but not for the rest of
the universe.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next reply other threads:[~2014-06-16 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 13:07 Borislav Petkov [this message]
2014-06-16 15:29 ` 3d3d6b847420 ("kbuild: LLVMLinux: Adapt warnings for compilation with clang") PaX Team
2014-06-16 15:48 ` Jan-Simon Möller
2014-06-29 20:13 ` Borislav Petkov
2014-07-01 0:42 ` [PATCH] kbuild, LLVMLinux: only use warnings when using clang behanw
2014-07-01 10:12 ` Borislav Petkov
2014-07-30 13:04 ` Michal Marek
2014-07-30 21:39 ` Behan Webster
2014-07-31 4:16 ` [PATCH v2] kbuild, LLVMLinux: Supress warnings unless W=1-3 behanw
2014-07-31 8:18 ` Michal Marek
2014-07-31 16:12 ` Behan Webster
2014-07-31 20:46 ` Michal Marek
2014-08-01 4:07 ` Behan Webster
2014-08-01 4:08 ` [PATCH v3] " behanw
2014-08-05 13:42 ` Michal Marek
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=20140616130751.GD8170@pd.tnic \
--to=bp@alien8.de \
--cc=behanw@converseincode.com \
--cc=dl9pf@gmx.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcharleb@gmail.com \
--cc=mmarek@suse.cz \
--cc=pageexec@freemail.hu \
/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.