Bug 1423 - Using -fno-strict-aliasing when compiling DPDK unit tests reduces their effectiveness
Summary: Using -fno-strict-aliasing when compiling DPDK unit tests reduces their effec...
Status: UNCONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: eventdev (show other bugs)
Version: 23.11
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: dev
URL:
Depends on:
Blocks:
 
Reported: 2024-04-28 09:29 CEST by Mattias Rönnblom
Modified: 2024-04-28 09:29 CEST (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Mattias Rönnblom 2024-04-28 09:29:09 CEST 
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.
Note You need to log in before you can comment on or make changes to this bug.