From: Jakub Jelinek <jakub@redhat.com>
To: Miika <nykseli@protonmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] Support for nonzero attribute
Date: Fri, 3 Jun 2022 18:45:28 +0200 [thread overview]
Message-ID: <Ypo6qAg0L19K+023@tucnak> (raw)
In-Reply-To: <jUYpPEW3Y9UZvEp25P0xyzRA4oaGxV_fPv6CkiFVUpCDLJlbKkXRTMeYWvmqSdIfFxO9GQedLgd0GVAikrAlG0yJ8nIl8w9ztCoXfWf2SHs=@protonmail.com>
On Fri, Jun 03, 2022 at 04:34:48PM +0000, Miika via Gcc wrote:
> Hello,
>
> I would like to add support for new attribute: nonzero.
> Nonzero attribute works the same way as nonnull but instead of checking for
> NULL, it checks for integer or enum with value 0.
NULL/nullptr is very special pointer (at it doesn't point to any object),
while integer with value 0 is just one of many possible values.
For some functions, 0 could be a value it wants to avoid, for others
such value could be -1, negative value, positive, whatever else...
IMHO if we want to add anything like this, it should be more generic,
specify that a particular argument must have value in a specific range.
Jakub
next prev parent reply other threads:[~2022-06-03 16:45 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 [this message]
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
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=Ypo6qAg0L19K+023@tucnak \
--to=jakub@redhat.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).