From: Emil Velikov <emil.l.velikov@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
emil.l.velikov@gmail.com,
Rikard Falkeborn <rikard.falkeborn@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: [PATCH v2] linux/bits.h: adjust GENMASK_INPUT_CHECK() check
Date: Tue, 19 May 2020 22:14:52 +0100 [thread overview]
Message-ID: <20200519211452.422179-1-emil.l.velikov@gmail.com> (raw)
In-Reply-To: <20200519101320.33495-1-emil.l.velikov@gmail.com>
Recently the GENMASK_INPUT_CHECK() was added, aiming to catch cases
where there GENMASK arguments are flipped.
Although it seems to be triggering -Wtype-limits in the following cases:
unsigned foo = (10 + x);
unsigned bar = GENMASK(foo, 0);
const unsigned foo = (10 + x);
unsigned bar = GENMASK(foo, 0);
Here are the warnings, from my GCC 9.2 box.
warning: comparison of unsigned expression < 0 is always false [-Wtype-limits]
__builtin_constant_p((l) > (h)), (l) > (h), 0)))
^
warning: comparison of unsigned expression < 0 is always false [-Wtype-limits]
__builtin_constant_p((l) > (h)), (l) > (h), 0)))
^
This results in people disabling the warning all together or promoting
foo to signed. Either of which being a sub par option IMHO.
Add a trivial "+ 1" to each h and l in the constant expression.
v2: drop accidental !
Fixes: 295bcca84916 ("linux/bits.h: add compile time sanity check of
GENMASK inputs")
Cc: Rikard Falkeborn <rikard.falkeborn@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
Reported-by: kbuild test robot <lkp@intel.com>
Reported-by: kbuild test robot <lkp@intel.com>
---
include/linux/bits.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/bits.h b/include/linux/bits.h
index 4671fbf28842..02a42866d198 100644
--- a/include/linux/bits.h
+++ b/include/linux/bits.h
@@ -23,7 +23,7 @@
#include <linux/build_bug.h>
#define GENMASK_INPUT_CHECK(h, l) \
(BUILD_BUG_ON_ZERO(__builtin_choose_expr( \
- __builtin_constant_p((l) > (h)), (l) > (h), 0)))
+ __builtin_constant_p((l + 1) > (h + 1)), (l + 1) > (h + 1), 0)))
#else
/*
* BUILD_BUG_ON_ZERO is not available in h files included from asm files,
--
2.25.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-19 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 10:13 [PATCH] linux/bits.h: adjust GENMASK_INPUT_CHECK() check Emil Velikov
2020-05-19 14:46 ` kbuild test robot
2020-05-19 15:04 ` kbuild test robot
2020-05-19 21:14 ` Emil Velikov [this message]
2020-05-19 21:28 ` [PATCH v2] " Rikard Falkeborn
2020-05-22 18:50 ` Emil Velikov
2020-05-23 19:35 ` Rikard Falkeborn
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=20200519211452.422179-1-emil.l.velikov@gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=rikard.falkeborn@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).