From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Subject: [PATCH 0/2] Address warnings from gcc 12.2 with -flto
Date: Wed, 28 Sep 2022 21:00:28 +0200 [thread overview]
Message-ID: <20220928190030.1379963-1-sbrivio@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
The first one is a bogus report of an uninitialised field passed as
input to hash functions for TCP connections, already seen with gcc 11.
The second one is a bogus stringop-overread which already happened
with gcc 12.1, but this time a "cute" pragma won't make it go away.
Both harmless, but noisy.
Based on pending series posted by David, if it matters.
Stefano Brivio (2):
Makefile: Extend noinline workarounds for LTO and -O2 to gcc 12
udp: Replace pragma to ignore bogus stringop-overread warning with
workaround
Makefile | 6 +++---
udp.c | 26 ++++++++++++++++++--------
util.h | 23 -----------------------
3 files changed, 21 insertions(+), 34 deletions(-)
--
2.35.1
next reply other threads:[~2022-09-28 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 19:00 Stefano Brivio [this message]
2022-09-28 19:00 ` [PATCH 1/2] Makefile: Extend noinline workarounds for LTO and -O2 to gcc 12 Stefano Brivio
2022-09-28 19:00 ` [PATCH 2/2] udp: Replace pragma to ignore bogus stringop-overread warning with workaround Stefano Brivio
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=20220928190030.1379963-1-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).