From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Xi Ruoyao <xry111@xry111.site>, libc-alpha@sourceware.org
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Carlos O'Donell <carlos@redhat.com>,
Alex Colomar <alx.manpages@gmail.com>,
Andreas Schwab <schwab@suse.de>,
Zack Weinberg <zack@owlfolio.org>,
Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] Revert "libio: Add __nonnull for FILE * arguments of fclose and freopen"
Date: Mon, 10 Jul 2023 18:34:13 -0400 [thread overview]
Message-ID: <f5620e20-f013-57fc-2476-d412f63919e2@gotplt.org> (raw)
In-Reply-To: <20230710220659.3501429-2-xry111@xry111.site>
On 2023-07-10 18:07, Xi Ruoyao wrote:
> This reverts commit 71d9e0fe766a3c22a730995b9d024960970670af.
>
> Apparantly the maintainers do not like __nonnull. And I'm too pissed
> off to work on this anymore. Anyway I don't care about the analyzer so
> they can just add these as ugly special analyzer patterns. And I'm not
> so stupid to pass NULL to these things myself, so lacking a warning is
> not a problem to me.
Sorry you feel this way, but this is still unresolved as we don't have a
consensus yet. However I understand if you're frustrated and don't want
to work on this for now; I do hope you return though.
In any case, if the consensus does steer towards never using
__nonnull__, it'll likely be better to do it by hacking cdefs.h to
expand __nonnull to nothing.
Thanks,
Sid
>
> Signed-off-by: Xi Ruoyao <xry111@xry111.site>
> ---
> libio/stdio.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/libio/stdio.h b/libio/stdio.h
> index 4cf9f1c012..2387590d6a 100644
> --- a/libio/stdio.h
> +++ b/libio/stdio.h
> @@ -180,7 +180,7 @@ extern int renameat2 (int __oldfd, const char *__old, int __newfd,
>
> This function is a possible cancellation point and therefore not
> marked with __THROW. */
> -extern int fclose (FILE *__stream) __nonnull ((1));
> +extern int fclose (FILE *__stream);
>
> #undef __attr_dealloc_fclose
> #define __attr_dealloc_fclose __attr_dealloc (fclose, 1)
> @@ -269,7 +269,7 @@ extern FILE *fopen (const char *__restrict __filename,
> marked with __THROW. */
> extern FILE *freopen (const char *__restrict __filename,
> const char *__restrict __modes,
> - FILE *__restrict __stream) __wur __nonnull ((3));
> + FILE *__restrict __stream) __wur;
> #else
> # ifdef __REDIRECT
> extern FILE *__REDIRECT (fopen, (const char *__restrict __filename,
> @@ -290,7 +290,7 @@ extern FILE *fopen64 (const char *__restrict __filename,
> __attribute_malloc__ __attr_dealloc_fclose __wur;
> extern FILE *freopen64 (const char *__restrict __filename,
> const char *__restrict __modes,
> - FILE *__restrict __stream) __wur __nonnull ((3));
> + FILE *__restrict __stream) __wur;
> #endif
>
> #ifdef __USE_POSIX
next prev parent reply other threads:[~2023-07-10 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 22:07 Xi Ruoyao
2023-07-10 22:34 ` Siddhesh Poyarekar [this message]
2023-07-11 0:31 ` Sam James
2023-07-11 5:15 ` Florian Weimer
2023-07-11 8:57 ` Florian Weimer
2023-07-11 11:20 ` Siddhesh Poyarekar
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=f5620e20-f013-57fc-2476-d412f63919e2@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=adhemerval.zanella@linaro.org \
--cc=alx.manpages@gmail.com \
--cc=carlos@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
--cc=xry111@xry111.site \
--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).