From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Lots and lots of potential bugs detected by GCC 14 analyzer
Date: Sun, 10 Nov 2024 15:16:44 -0800 [thread overview]
Message-ID: <20241110151644.76e5739e@hermes.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
If -fanalyzer is added to config/meson.build than compiler finds lots of potential
problems. (Think of it as free version of Coverity).
The output is quite verbose.
Is it worth putting large N of new bugs into bugzilla or maybe maintainers could take a look.
Full build output is 12M so attaching it.
Quick hack to enable is.
diff --git a/config/meson.build b/config/meson.build
index 5095d2fbcb..43c2a6d97b 100644
--- a/config/meson.build
+++ b/config/meson.build
@@ -308,6 +308,8 @@ endif
# -Wall is added by default at warning level 1, and -Wextra
# at warning level 2 (DPDK default)
warning_flags = [
+ '-fanalyzer',
+
# additional warnings in alphabetical order
'-Wcast-qual',
'-Wdeprecated',
~/DPDK/main $
[-- Attachment #2: build.out.gz --]
[-- Type: application/gzip, Size: 843401 bytes --]
reply other threads:[~2024-11-12 9:06 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241110151644.76e5739e@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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 NNTP newsgroup(s).