DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/eventdev Bug 1576] [dpdk24.11-rc2] DPDK build failed with EXTRA_CFLAGS='-O1' on Redhat9.4
Date: Thu, 23 Jan 2025 07:41:13 +0000	[thread overview]
Message-ID: <bug-1576-3-ZUzwDMbe68@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1576-3@http.bugs.dpdk.org/>

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1576

tingtingx.liao@intel.com (tingtingx.liao@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from tingtingx.liao@intel.com (tingtingx.liao@intel.com) ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3759 bytes --]

      reply	other threads:[~2025-01-23  7:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13  9:08 bugzilla
2025-01-23  7:41 ` bugzilla [this message]

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-1576-3-ZUzwDMbe68@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).