From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: [PATCH 2/2] ring: remove GCC pragma
Date: Tue, 20 Oct 2026 07:55:41 -0700 [thread overview]
Message-ID: <20261020145541.388371-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20261020145541.388371-1-stephen@networkplumber.org>
The original issue that required using pragma here to disable
stringop warnings is now handled at in config/meson.build
across all files.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/ring/rte_ring_elem_pvt.h | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/lib/ring/rte_ring_elem_pvt.h b/lib/ring/rte_ring_elem_pvt.h
index 29758d0bb8..3d680749ad 100644
--- a/lib/ring/rte_ring_elem_pvt.h
+++ b/lib/ring/rte_ring_elem_pvt.h
@@ -10,12 +10,6 @@
#ifndef _RTE_RING_ELEM_PVT_H_
#define _RTE_RING_ELEM_PVT_H_
-#if defined(RTE_TOOLCHAIN_GCC) && (GCC_VERSION >= 120000)
-#pragma GCC diagnostic push
-#pragma GCC diagnostic ignored "-Wstringop-overflow"
-#pragma GCC diagnostic ignored "-Wstringop-overread"
-#endif
-
static __rte_always_inline void
__rte_ring_enqueue_elems_32(void *ring_table, const void *obj_table,
uint32_t size, uint32_t idx, uint32_t n)
@@ -500,8 +494,4 @@ __rte_ring_do_dequeue_elem(struct rte_ring *r, void *obj_table,
return n;
}
-#if defined(RTE_TOOLCHAIN_GCC) && (GCC_VERSION >= 120000)
-#pragma GCC diagnostic pop
-#endif
-
#endif /* _RTE_RING_ELEM_PVT_H_ */
--
2.53.0
next prev parent reply other threads:[~2026-10-20 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 14:55 [PATCH 1/2] build: disable GCC string op warnings when unoptimized Stephen Hemminger
2026-10-20 14:55 ` Stephen Hemminger [this message]
2026-10-20 15:33 ` Morten Brørup
2026-10-20 18:01 ` Stephen Hemminger
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=20261020145541.388371-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=wathsala.vithanage@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.