All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1512] event/octeontx build failure on Ubuntu 24.04 with LTO
Date: Sun, 04 Aug 2024 21:01:20 +0000	[thread overview]
Message-ID: <bug-1512-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1512
           Summary: event/octeontx build failure on Ubuntu 24.04 with LTO
           Product: DPDK
           Version: 24.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

$ meson --werror -Db_lto=true build && ninja -C build
[..]
In function ‘ssovf_parsekv’,
    inlined from ‘rte_kvargs_process’ at ../lib/kvargs/rte_kvargs.c:188:9,
    inlined from ‘ssovf_vdev_probe’ at
../drivers/event/octeontx/ssovf_evdev.c:872:10:
../drivers/event/octeontx/ssovf_evdev.c:723:15: warning: writing 4 bytes into a
region of size 1 [-Wstringop-overflow=]
  723 |         *flag = !!atoi(value);
      |               ^
../drivers/event/octeontx/ssovf_evdev.c: In function ‘ssovf_vdev_probe’:
../drivers/event/octeontx/ssovf_evdev.c:26:16: note: destination object
‘timvf_enable_stats’ of size 1
[..]

OS: Ubuntu 24.04
Meson: 1.3.2
Compiler: gcc 13.2.0

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

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

             reply	other threads:[~2024-08-04 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04 21:01 bugzilla [this message]
2024-09-12  5:32 ` [DPDK/ethdev Bug 1512] event/octeontx build failure on Ubuntu 24.04 with LTO 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-1512-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.