DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1149] [21.11] lib/ring build failure with gcc 12 and debug enabled
Date: Thu, 15 Dec 2022 17:40:50 +0000	[thread overview]
Message-ID: <bug-1149-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1149
           Summary: [21.11] lib/ring build failure with gcc 12 and debug
                    enabled
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

$ meson --werror --buildtype=debug -Dc_args='-DRTE_ENABLE_ASSERT
-DRTE_LIBRTE_MLX4_DEBUG -DRTE_LIBRTE_MLX5_DEBUG' build && ninja-build -C build

[..]
lib/ring/rte_ring_elem_pvt.h:100:25: error: 'memcpy' reading 32 bytes from a
region of size 4 [-Werror=stringop-overread]
[..]

DPDK: 0c553ce527
OS: Fedora 38
gcc: 12.2.1

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

             reply	other threads:[~2022-12-15 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 17:40 bugzilla [this message]
2022-12-21  7:36 ` bugzilla

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-1149-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 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).