This issue has been fixed on higher versions of gcc(14.2+)
And by the description of the following comment, will close this ticket.
Comments from developers:
The warning message is due to the fact that the assembly code generated by GCC
may skip the initialization of the event variable at the O1 optimization, but
was replaced by other instructions in O2 and O3, therefore it compiles fine.
This issue does not need to be fixed considering the following reasons.
1. There is a rte_memcpy() at line number 699 which is copying response
information as event into this. So, that will initialize all the event fields.
We don't require to initialize events at the declaration.
2. O1 is an unusual, the default optimization level of DPDK is O3, the
functions in the report are inline functions, they will be integrated into
their callers at this level, skipping the initialization is not possible.
3. These warning messages appear only in the O1 optimization and not in O2 and
O3.
4. The compiler in JIRA is GCC 11.4.1, and there are no warning messages when
using Clang 19.1.3 and higher versions of GCC 14.2.1.
This issue has been fixed on higher versions of gcc(14.2+) And by the description of the following comment, will close this ticket. Comments from developers: The warning message is due to the fact that the assembly code generated by GCC may skip the initialization of the event variable at the O1 optimization, but was replaced by other instructions in O2 and O3, therefore it compiles fine. This issue does not need to be fixed considering the following reasons. 1. There is a rte_memcpy() at line number 699 which is copying response information as event into this. So, that will initialize all the event fields. We don't require to initialize events at the declaration. 2. O1 is an unusual, the default optimization level of DPDK is O3, the functions in the report are inline functions, they will be integrated into their callers at this level, skipping the initialization is not possible. 3. These warning messages appear only in the O1 optimization and not in O2 and O3. 4. The compiler in JIRA is GCC 11.4.1, and there are no warning messages when using Clang 19.1.3 and higher versions of GCC 14.2.1.