From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH] manywarnings: enable some malloc warnings
Date: Mon, 2 Aug 2021 16:50:00 -0700 [thread overview]
Message-ID: <20210802235000.158077-1-eggert@cs.ucla.edu> (raw)
* m4/manywarnings.m4 (gl_MANYWARN_ALL_GCC): Stop adding
-Wno-analyzer-double-free, -Wno-analyzer-null-dereference, and
-Wno-analyzer-use-after-free, as these false alarms don’t seem
to be as much of an issue now that we’ve pacified a couple
of individual modules and GCC has some bug fixes.
---
ChangeLog | 7 +++++++
m4/manywarnings.m4 | 12 +++---------
2 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index d4025b64e..06f139a54 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,12 @@
2021-08-02 Paul Eggert <eggert@cs.ucla.edu>
+ manywarnings: enable some malloc warnings
+ * m4/manywarnings.m4 (gl_MANYWARN_ALL_GCC): Stop adding
+ -Wno-analyzer-double-free, -Wno-analyzer-null-dereference, and
+ -Wno-analyzer-use-after-free, as these false alarms don’t seem
+ to be as much of an issue now that we’ve pacified a couple
+ of individual modules and GCC has some bug fixes.
+
dfa: omit unneeded malloc+free
Problem indirectly found by Coverity.
* lib/dfa.c (enlistnew): New function, with most of the body of
diff --git a/m4/manywarnings.m4 b/m4/manywarnings.m4
index 611484f31..872ea58e6 100644
--- a/m4/manywarnings.m4
+++ b/m4/manywarnings.m4
@@ -1,4 +1,4 @@
-# manywarnings.m4 serial 22
+# manywarnings.m4 serial 23
dnl Copyright (C) 2008-2021 Free Software Foundation, Inc.
dnl This file is free software; the Free Software Foundation
dnl gives unlimited permission to copy and/or distribute it,
@@ -195,15 +195,9 @@ AC_DEFUN([gl_MANYWARN_ALL_GCC(C)],
gl_AS_VAR_APPEND([$1], [' -Wno-uninitialized'])
fi
- # Some warnings have too many false alarms in GCC 10.1.
- # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93695
- gl_AS_VAR_APPEND([$1], [' -Wno-analyzer-double-free'])
- # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101713 (GCC 11.2.1)
+ # This warning have too many false alarms in GCC 11.2.1.
+ # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101713
gl_AS_VAR_APPEND([$1], [' -Wno-analyzer-malloc-leak'])
- # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94851
- gl_AS_VAR_APPEND([$1], [' -Wno-analyzer-null-dereference'])
- # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95758
- gl_AS_VAR_APPEND([$1], [' -Wno-analyzer-use-after-free'])
AC_LANG_POP([C])
])
--
2.31.1
reply other threads:[~2021-08-02 23:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210802235000.158077-1-eggert@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.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).