From: Miika <nykseli@protonmail.com>
To: Ben Boeckel <ben.boeckel@kitware.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: [RFC] Support for nonzero attribute
Date: Tue, 07 Jun 2022 19:39:33 +0000 [thread overview]
Message-ID: <hapHPesrXynIutXX68P4QEdXuawT26fUD2ddjC_F7e6E7gCoAP-v5oh3QjWIXciEm8_MJyQBWxMFZGFcqR9uTDVMJQTfOWhyCytjTI6lKXo=@protonmail.com> (raw)
In-Reply-To: <Yp5KpUw7ckPJPs2Q@farprobe>
On Monday, June 6th, 2022 at 9:42 PM, Ben Boeckel <ben.boeckel@kitware.com> 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)?
I took a closer look at it and looks like it can be applied.
So trying to compile this:
```
typedef int __attribute__((inrange(0, 100))) percentage_t;
int main() {
int percentage __attribute__((inrange(0, 100))) = -1;
percentage_t per __attribute__((inrange(0, 100))) = -1;
}
```
Would print out something like this:
foo.c: In function 'main':
foo.c:3:59: warning: inrange variable 'percentage' requires integer in rage of 0..100 [-Winrange]
3 | int percentage __attribute__((inrange(0, 100))) = -1;
| ^
foo.c:4:61: warning: inrange variable 'per' requires integer in rage of 0..100 [-Winrange]
4 | percentage_t per __attribute__((inrange(0, 100))) = -1;
|
Miika
next prev parent reply other threads:[~2022-06-07 19:39 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
2022-06-07 19:39 ` Miika [this message]
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='hapHPesrXynIutXX68P4QEdXuawT26fUD2ddjC_F7e6E7gCoAP-v5oh3QjWIXciEm8_MJyQBWxMFZGFcqR9uTDVMJQTfOWhyCytjTI6lKXo=@protonmail.com' \
--to=nykseli@protonmail.com \
--cc=ben.boeckel@kitware.com \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).