From: Eric Gallager <egall@gwmail.gwu.edu>
To: Miika <nykseli@protonmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [RFC] Support for nonzero attribute
Date: Thu, 9 Jun 2022 00:36:28 -0400 [thread overview]
Message-ID: <CAMfHzOsrBV6y4gKFnE+SwnkJXGtnGQBwK0-B5uR9kjsb9zN32g@mail.gmail.com> (raw)
In-Reply-To: <Twq42pgiAlAoPaGUXZQHMISdmYGcf9p8tPODqGE3nhGQbVu7S6lEu6tNllYNUJGQyQuRnfAlSduCQiRiZXbAXkQy6Hn8hkHZK9tkYQtCMsw=@protonmail.com>
On Wed, Jun 8, 2022 at 5:00 PM Miika <nykseli@protonmail.com> wrote:
>
> On Wednesday, June 8th, 2022 at 8:42 PM, Eric Gallager <egall@gwmail.gwu.edu> wrote:
> > Could you take a look at bug 78155 too? There was a request to add
> > something like this in that bug:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78155
> > (and I think I've seen similar requests elsewhere, too)
>
> I took a look at the bug and looks like the inrange attribute can be applied to
> builtin functions too.
>
> So now the example code
> int main (void)
> {
> __builtin_printf ("%i\n", __builtin_isalpha (999999));
> }
>
> Now gives the following error:
>
> foo.c: In function 'main':
> foo.c:3:31: warning: argument in position 1 not in rage of 0..255 [-Winrange]
> 3 | __builtin_printf ("%i\n", __builtin_isalpha (999999));
> |
>
> Miika
Nice, good to hear! I'm looking forward to seeing this get added!
Thanks,
Eric
next prev parent reply other threads:[~2022-06-09 4:36 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
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 [this message]
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=CAMfHzOsrBV6y4gKFnE+SwnkJXGtnGQBwK0-B5uR9kjsb9zN32g@mail.gmail.com \
--to=egall@gwmail.gwu.edu \
--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).