From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org, Jim Meyering <jim@meyering.net>
Subject: Re: vasnprintf.c vs GCC11's -Wanalyzer-null-argument (and glibc-2.31)
Date: Sun, 03 Jan 2021 05:04:20 +0100 [thread overview]
Message-ID: <4562905.TRXkJnkmrF@omega> (raw)
In-Reply-To: <9391b43b-e6e1-9aee-833c-be719a3083fd@cs.ucla.edu>
Paul Eggert wrote:
> I'd rather not work around those bugs as we can just ask
> people to use --disable-gcc-warnings if their GCC is old.
Yes. Or to set CPPFLAGS="-fno-analyzer" with GCC >= 10.
Bruno
next prev parent reply other threads:[~2021-01-03 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 1:11 vasnprintf.c vs GCC11's -Wanalyzer-null-argument (and glibc-2.31) Jim Meyering
2021-01-03 1:49 ` Bruno Haible
2021-01-03 1:54 ` Bruno Haible
2021-01-03 3:21 ` Paul Eggert
2021-01-03 4:04 ` Bruno Haible [this message]
2021-01-03 7:11 ` Jim Meyering
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4562905.TRXkJnkmrF@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jim@meyering.net \
/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).