All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1863] common/cnxk: build errors with LTO
Date: Wed, 31 Dec 2025 18:23:51 +0000	[thread overview]
Message-ID: <bug-1863-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1863

            Bug ID: 1863
           Summary: common/cnxk: build errors with LTO
           Product: DPDK
           Version: 25.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

Doing LTO release build detects errors in irq

../drivers/common/cnxk/roc_platform.c: In function ‘irq_config’:
../drivers/common/cnxk/roc_platform.c:56:14: warning: argument to
variable-length array is too large [-Wvla-larger-than=]
   56 |         char irq_set_buf[MSIX_IRQ_SET_BUF_LEN];
      |              ^
../drivers/common/cnxk/roc_platform.c:56:14: note: limit is 9223372036854775807
bytes, but argument is 18446744073709551548
../drivers/common/cnxk/roc_platform.c: In function ‘irq_init’:
../drivers/common/cnxk/roc_platform.c:92:14: warning: argument to
variable-length array is too large [-Wvla-larger-than=]
   92 |         char irq_set_buf[MSIX_IRQ_SET_BUF_LEN];
      |              ^
../drivers/common/cnxk/roc_platform.c:92:14: note: limit is 9223372036854775807
bytes, but argument is 18446744073709551548

Looks like MSIX_IRQ_SET_BUF_LEN is not a constant??

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

             reply	other threads:[~2025-12-31 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31 18:23 bugzilla [this message]
2026-01-19 19:57 ` [DPDK/ethdev Bug 1863] common/cnxk: build errors 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-1863-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.