public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Miika <nykseli@protonmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: [RFC] Support for nonzero attribute
Date: Sat, 04 Jun 2022 11:25:33 +0000	[thread overview]
Message-ID: <JUX7HdHj_a0DdYc9QUShwc8hy5O1Yx5DfdDsT9kNU7ehMJeOK1x3rwF5L15BfBEl_4P-VmgjktCuxwFg_wF8ESwghS6jpfEN6zrk5kPnaQ8=@protonmail.com> (raw)
In-Reply-To: <Ypo6qAg0L19K+023@tucnak>

Thank you for the feedback!

On Friday, June 3rd, 2022 at 7:45 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> 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.

That's a really good point. Making it generic makes a lot more sense.
I'll try to design some kind of a range attribute and see how it feels.

  reply	other threads:[~2022-06-04 11:25 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 [this message]
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='JUX7HdHj_a0DdYc9QUShwc8hy5O1Yx5DfdDsT9kNU7ehMJeOK1x3rwF5L15BfBEl_4P-VmgjktCuxwFg_wF8ESwghS6jpfEN6zrk5kPnaQ8=@protonmail.com' \
    --to=nykseli@protonmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.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).