From: Xi Ruoyao <xry111@xry111.site>
To: Alejandro Colomar <alx@kernel.org>, Martin Uecker <muecker@gwdg.de>
Cc: Andrew Pinski <pinskia@gmail.com>,
GNU libc development <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Carlos O'Donell <carlos@redhat.com>,
Andreas Schwab <schwab@suse.de>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
Zack Weinberg <zack@owlfolio.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, enh <enh@google.com>
Subject: Re: ISO C's [static] (was: _Nullable and _Nonnull in GCC's analyzer)
Date: Wed, 09 Aug 2023 21:46:17 +0800 [thread overview]
Message-ID: <0cef403e12afc400aabc904d1f2d4b69f7837372.camel@xry111.site> (raw)
In-Reply-To: <a213b674-2469-30e2-0e01-4c399fd0d47f@kernel.org>
On Wed, 2023-08-09 at 12:42 +0200, Alejandro Colomar wrote:
> I have a gripe with ISO C's [static]. As you mention, ISO
> conflated two functionalities in [static]:
>
> - The size of the array passed as argument must not be less
> than the size specified in the parameter's [].
>
> - The pointer must not be NULL.
https://gcc.gnu.org/pipermail/gcc-patches/2023-July/625559.html
If this patch is merged, they'll just become __nonnull and have all
advantages and disadvantages as __nonnull.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-08-09 13:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 16:13 [PATCH v5] libio: Add nonnull attribute for most FILE * arguments in stdio.h Xi Ruoyao
2023-07-10 17:12 ` Zack Weinberg
2023-07-10 17:27 ` Xi Ruoyao
2023-07-10 19:06 ` Zack Weinberg
2023-07-10 19:31 ` Xi Ruoyao
2023-07-10 17:51 ` Siddhesh Poyarekar
2023-07-10 18:41 ` Xi Ruoyao
2023-07-10 20:14 ` _Nullable and _Nonnull in GCC's analyzer (was: [PATCH v5] libio: Add nonnull attribute for most FILE * arguments in stdio.h) Alejandro Colomar
2023-07-10 20:16 ` Alejandro Colomar
2023-08-08 10:01 ` Martin Uecker
2023-08-09 0:14 ` enh
2023-08-09 1:11 ` Siddhesh Poyarekar
2023-08-09 7:26 ` Martin Uecker
2023-08-09 10:42 ` ISO C's [static] (was: _Nullable and _Nonnull in GCC's analyzer) Alejandro Colomar
2023-08-09 12:03 ` Martin Uecker
2023-08-09 12:37 ` Alejandro Colomar
2023-08-09 14:24 ` Martin Uecker
2023-08-09 13:46 ` Xi Ruoyao [this message]
2023-08-11 23:34 ` _Nullable and _Nonnull in GCC's analyzer (was: [PATCH v5] libio: Add nonnull attribute for most FILE * arguments in stdio.h) enh
2023-07-10 18:56 ` [PATCH v5] libio: Add nonnull attribute for most FILE * arguments in stdio.h Zack Weinberg
2023-07-10 19:31 ` Siddhesh Poyarekar
2023-07-10 19:35 ` Xi Ruoyao
2023-07-10 19:46 ` Siddhesh Poyarekar
2023-07-10 20:23 ` Xi Ruoyao
2023-07-10 20:33 ` Jeff Law
2023-07-10 20:44 ` Xi Ruoyao
2023-07-10 20:55 ` Zack Weinberg
2023-07-10 21:03 ` Xi Ruoyao
2023-07-10 21:22 ` Zack Weinberg
2023-07-10 21:33 ` Xi Ruoyao
2023-07-11 19:12 ` Zack Weinberg
2023-07-11 20:12 ` Siddhesh Poyarekar
2023-07-12 8:59 ` Xi Ruoyao
2023-07-10 22:09 ` Paul Eggert
2023-07-11 19:18 ` Zack Weinberg
2023-07-11 20:45 ` Jeff Law
2023-07-11 23:59 ` Paul Eggert
2023-07-12 2:40 ` Jeff Law
2023-07-10 22:48 ` Siddhesh Poyarekar
2023-07-11 0:45 ` Sam James
2023-07-10 21:51 ` Jeff Law
2023-07-11 13:03 ` Cristian Rodríguez
2023-07-10 22:34 ` Siddhesh Poyarekar
2023-07-10 22:59 ` Jeff Law
2023-07-11 0:51 ` Sam James
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=0cef403e12afc400aabc904d1f2d4b69f7837372.camel@xry111.site \
--to=xry111@xry111.site \
--cc=adhemerval.zanella@linaro.org \
--cc=alx@kernel.org \
--cc=carlos@redhat.com \
--cc=enh@google.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=muecker@gwdg.de \
--cc=pinskia@gmail.com \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.org \
--cc=zack@owlfolio.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).