From: Nathan Chancellor <nathan@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kbuild@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH 1/2] drm/i915: drop -Wall and related disables from cflags as redundant
Date: Mon, 9 Oct 2023 09:38:37 -0700 [thread overview]
Message-ID: <20231009163837.GA1153868@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CAK7LNAT6MzbcjR7KZMEFUCHkq+WXgTB=Qmp_VD4UC7TvMg+dMg@mail.gmail.com>
On Sun, Oct 08, 2023 at 12:28:46AM +0900, Masahiro Yamada wrote:
> On Fri, Oct 6, 2023 at 9:35 PM Jani Nikula <jani.nikula@intel.com> wrote:
> >
> > The kernel top level Makefile, and recently scripts/Makefile.extrawarn,
> > have included -Wall, and the disables -Wno-format-security and
> > $(call cc-disable-warning,frame-address,) for a very long time. They're
> > redundant in our local subdir-ccflags-y and can be dropped.
> >
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: Nick Desaulniers <ndesaulniers@google.com>
> > Cc: Nathan Chancellor <nathan@kernel.org>
> > Cc: Masahiro Yamada <masahiroy@kernel.org>
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
>
> I made a similar suggestion in the past
> https://lore.kernel.org/dri-devel/20190515043753.9853-1-yamada.masahiro@socionext.com/
>
> So, I am glad that Intel has decided to de-duplicate the flags.
>
>
>
> I think you can drop more flags.
>
> For example,
>
> subdir-ccflags-y += -Wno-sign-compare
>
>
> It is set by scripts/Makefile.extrawarn
> unless W=3 is passed.
>
>
> If W=3 is set by a user, -Wsign-compare should be warned
> as it is the user's request.
>
>
> drivers/gpu/drm/i915/Makefile negates W=3.
> There is no good reason to do so.
>
>
> Same applied to
>
>
> subdir-ccflags-y += -Wno-shift-negative-value
As I point out in my review of the second patch [1], I am not sure these
should be dropped because -Wextra turns these warnings back on, at least
for clang according to this build report [2] and my own testing, so they
need to be disabled again.
[1]: https://lore.kernel.org/20231006174550.GC3359308@dev-arch.thelio-3990X/
[2]: https://lore.kernel.org/202310070011.Fji48IBk-lkp@intel.com/
Cheers,
Nathan.
next prev parent reply other threads:[~2023-10-09 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 12:34 [PATCH 0/2] drm/i915: align with W=1 warnings Jani Nikula
2023-10-06 12:34 ` [PATCH 1/2] drm/i915: drop -Wall and related disables from cflags as redundant Jani Nikula
2023-10-06 17:02 ` Nathan Chancellor
2023-10-06 21:12 ` Nick Desaulniers
2023-10-07 15:28 ` Masahiro Yamada
2023-10-09 16:38 ` Nathan Chancellor [this message]
2023-10-10 8:29 ` Jani Nikula
2023-10-10 8:49 ` [Intel-gfx] " Jani Nikula
2023-10-10 15:46 ` Nick Desaulniers
2023-10-11 7:31 ` Jani Nikula
2023-10-06 12:34 ` [PATCH 2/2] drm/i915: enable W=1 warnings by default Jani Nikula
2023-10-06 16:49 ` [Intel-gfx] " kernel test robot
2023-10-06 17:45 ` Nathan Chancellor
2023-10-10 8:33 ` Jani Nikula
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=20231009163837.GA1153868@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox