From: Ben Boeckel <ben.boeckel@kitware.com>
To: Miika <nykseli@protonmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] Support for nonzero attribute
Date: Mon, 6 Jun 2022 14:42:45 -0400 [thread overview]
Message-ID: <Yp5KpUw7ckPJPs2Q@farprobe> (raw)
In-Reply-To: <6PeOfngSW_gLKMPtqp7UWs9ZQRv6KpLer221P_B9lNGGC7nJD0p-ta_7b0fwgSdz6cw7UzXsO0OGg0t2UUux81cVfIZkQcbjPwcRHFsNomI=@protonmail.com>
On Sun, Jun 05, 2022 at 20:09:04 +0000, Miika via Gcc wrote:
> Based on Jakub's and Yair's comments I created a new attribute "inrange".
> Inrage takes three arguments, pos min and max.
> Pos being the argument position in the function, and min and max defines the
> range of valid integer. Both min and max are inclusive and work with enums.
> Warnings are enabled with the new flag: "-Winrange".
Is this something that could be applied to variables or types (I've not
much experience with GCC attribute internal mechanisms, so maybe not)?
For example:
```
// This variable must be in range.
int percentage __attribute__((inrange(0, 100)));
// Any variable declared through this typedef must be in range.
typedef int __attribute__((inrange(0, 100))) percentage_t;
```
--Ben
next prev parent reply other threads:[~2022-06-06 18:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 16:34 Miika
2022-06-03 16:45 ` Jakub Jelinek
2022-06-04 11:25 ` Miika
2022-06-05 20:09 ` Miika
2022-06-06 18:42 ` Ben Boeckel [this message]
2022-06-07 19:39 ` Miika
2022-06-07 19:44 ` Jonathan Wakely
2022-06-07 19:46 ` Jonathan Wakely
2022-06-07 19:56 ` Miika
2022-06-08 17:42 ` Eric Gallager
2022-06-08 20:59 ` Miika
2022-06-09 4:36 ` Eric Gallager
2022-06-09 18:06 ` Miika
2022-06-12 4:25 ` Prathamesh Kulkarni
2022-06-13 12:55 ` Miika
2022-06-13 16:02 ` Martin Sebor
[not found] <mailman.2312.1654300374.1672222.gcc@gcc.gnu.org>
2022-06-04 10:26 ` Yair Lenga
2022-06-04 11:55 ` Miika
2022-06-04 21:29 ` Yair Lenga
2022-06-13 9:49 ` Richard Biener
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=Yp5KpUw7ckPJPs2Q@farprobe \
--to=ben.boeckel@kitware.com \
--cc=gcc@gcc.gnu.org \
--cc=nykseli@protonmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).