From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/eventdev Bug 1423] Using -fno-strict-aliasing when compiling DPDK unit tests reduces their effectiveness
Date: Sun, 28 Apr 2024 07:29:09 +0000 [thread overview]
Message-ID: <bug-1423-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1423
Bug ID: 1423
Summary: Using -fno-strict-aliasing when compiling DPDK unit
tests reduces their effectiveness
Product: DPDK
Version: 23.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: eventdev
Assignee: dev@dpdk.org
Reporter: mattias.ronnblom@ericsson.com
Target Milestone: ---
6b89650418f adds
+# Strict-aliasing rules are violated by uint8_t[] to context size casts.
+CFLAGS += -fno-strict-aliasing
to app/test/meson.build.
This flag applies to all tests, not just the broken RTE graph tests (or SUT?).
Passing this flag to the compiler will prevent any functional tests (of any
component) from detecting any aliasing-related bugs found in code located in
SUT header files.
RTE graph should be fixed, rather than a whole-sale application of this
work-around to DPDK test suite.
In additional, reducing the level of compiler optimization will make the perf
test less relevant.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3124 bytes --]
reply other threads:[~2024-04-28 7:29 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=bug-1423-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.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 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.