public inbox for linux-sparse@vger.kernel.org
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Vincent Mailhol' <mailhol.vincent@wanadoo.fr>,
	'Linus Torvalds' <torvalds@linux-foundation.org>,
	'Yury Norov' <yury.norov@gmail.com>,
	"'Rasmus Villemoes'" <linux@rasmusvillemoes.dk>,
	'Luc Van Oostenryck' <luc.vanoostenryck@gmail.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-sparse@vger.kernel.org'" <linux-sparse@vger.kernel.org>,
	"'Rikard Falkeborn'" <rikard.falkeborn@gmail.com>
Subject: RE: [PATCH v4 2/2] linux/bits.h: simplify GENMASK_INPUT_CHECK()
Date: Sun, 17 Nov 2024 19:45:56 +0000	[thread overview]
Message-ID: <f5692429eb4b43738f562e5fc402ead2@AcuMS.aculab.com> (raw)
In-Reply-To: <8bf9eb4434104a3b960d52bd1d38caea@AcuMS.aculab.com>

From: David Laight
> Sent: 17 November 2024 17:25
> 
> From: Vincent Mailhol
> > Sent: 13 November 2024 17:19
> >
> > In GENMASK_INPUT_CHECK(),
> >
> >   __builtin_choose_expr(__is_constexpr((l) > (h)), (l) > (h), 0)
> >
> > is the exact expansion of:
> >
> >   const_true((l) > (h))
> >
> > Apply const_true() to simplify GENMASK_INPUT_CHECK().
> 
> Wouldn't statically_true() give better coverage ?
> I wouldn't have though that GENMASK() got used anywhere where a constant
> integer expression was needed.

If it is, maybe add a GENMASK_CONST() that uses BUILD_BUG_ON_ZERO_MSG()
(recently proposed) and so validates that the values are constants.
And then use statically_true() in the normal case to pick up more errors.

(Or just remove the check because coders really aren't that stupid!)

The interesting cases are the ones using variables.
And they'd need run-time checks of some form.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)


  reply	other threads:[~2024-11-17 19:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 17:18 [PATCH v4 0/2] add const_true() to simplify GENMASK_INPUT_CHECK() Vincent Mailhol
2024-11-13 17:18 ` [PATCH v4 1/2] compiler.h: add const_true() Vincent Mailhol
2024-11-13 18:53   ` Yury Norov
2024-12-30 18:32     ` Yury Norov
2024-12-31  4:58       ` Vincent Mailhol
2024-11-17 17:42   ` David Laight
2024-11-17 18:00     ` Linus Torvalds
2024-11-17 19:02       ` Linus Torvalds
2024-11-17 19:05       ` David Laight
2024-11-17 19:09         ` Linus Torvalds
2024-11-17 19:23           ` David Laight
2024-11-17 20:12             ` Linus Torvalds
2024-11-17 22:38               ` David Laight
2024-11-17 22:58                 ` Linus Torvalds
2024-11-18  3:22                   ` Vincent Mailhol
2024-11-18  9:27                     ` David Laight
2024-11-18 17:09                     ` Linus Torvalds
2024-11-13 17:18 ` [PATCH v4 2/2] linux/bits.h: simplify GENMASK_INPUT_CHECK() Vincent Mailhol
2024-11-17 17:24   ` David Laight
2024-11-17 19:45     ` David Laight [this message]
2024-11-18  1:14       ` Vincent Mailhol
2024-11-18  1:12     ` Vincent Mailhol

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=f5692429eb4b43738f562e5fc402ead2@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=rikard.falkeborn@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yury.norov@gmail.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