bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Jim Meyering <jim@meyering.net>
Subject: Re: vasnprintf.c vs GCC11's -Wanalyzer-null-argument (and glibc-2.31)
Date: Sun, 03 Jan 2021 02:54:23 +0100	[thread overview]
Message-ID: <3737660.3Hbm7dB2au@omega> (raw)
In-Reply-To: <2624561.TfKlLiq1dV@omega>

When I wrote:
> So, in the current state, looking at -fanalyzer / -Wanalyzer outputs is
> still a waste of time.

I meant this with respect to Gnulib source code, which is usually reviewed
by 2 people, which has unit tests, and so on.

It is well possible that -fanalyzer / -Wanalyzer is useful to find simple
coding mistakes in other packages.

Bruno



  reply	other threads:[~2021-01-03  1:54 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 [this message]
2021-01-03  3:21   ` Paul Eggert
2021-01-03  4:04     ` Bruno Haible
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=3737660.3Hbm7dB2au@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --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).