Using -fno-strict-aliasing when compiling DPDK unit tests reduces their effectiveness

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: [email protected]
Reporter: [email protected]
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.