DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1039] [dpdk 22.07-rc0] drivers/vdpa/ifc meson build failed with gcc12.1.1 on Fedora36/64
Date: Mon, 20 Jun 2022 06:10:42 +0000	[thread overview]
Message-ID: <bug-1039-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1039
           Summary: [dpdk 22.07-rc0] drivers/vdpa/ifc meson build failed
                    with gcc12.1.1 on Fedora36/64
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: daxuex.gao@intel.com
  Target Milestone: ---

[dpdk version]
dpdk 22.07-rc1

commit b38db1bfb930fa27cfbc36db227b56c1c1613164 (HEAD -> main, origin/main,
origin/HEAD)
Author: Tomasz Duszynski <tduszynski@marvell.com>
Date:   Sat Jun 4 18:31:57 2022 +0200

    common/cnxk: allow building for generic arm64

    Allow building generic arm64 target using config/arm/arm64_armv8_linux_*
    config which works on both cn9k and cn10k by relaxing cache line size
    requirements a bit.

    While at it move cache line checks to common place.

    Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
    Reviewed-by: Jerin Jacob <jerinj@marvell.com>

[Bad commit]
This is a problem on a new os, no problem on fedora35

[OS version]
Fedora Linux 36/5.17.7-300.fc36.x86_64
GCC12.1.1

[Test setup]
git pw series apply 23389 --exclude=doc/**
git pw series apply 23424 --exclude=doc/**
git pw series apply 23574 --exclude=doc/**
git pw series apply 23613 --exclude=doc/**
meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all
--default-library=static gcc-linux-app 
ninja -C gcc-linux-app

[log]
[2507/3588] Compiling C object
drivers/libtmp_rte_vdpa_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o
FAILED: drivers/libtmp_rte_vdpa_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o
cc -Idrivers/libtmp_rte_vdpa_ifc.a.p -Idrivers -I../drivers -Idrivers/vdpa/ifc
-I../drivers/vdpa/ifc -I../drivers/vdpa/ifc/base -Idrivers/bus/pci
-I../drivers/bus/pci -I../drivers/bus/pci/linux -I. -I.. -Iconfig -I../config
-Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include
-I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include
-Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs
-I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry
-I../lib/telemetry -Ilib/pci -I../lib/pci -Ilib/vhost -I../lib/vhost
-Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf
-Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter
-I../lib/meter -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu
-Ilib/hash -I../lib/hash -Ilib/dmadev -I../lib/dmadev
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra
-Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat
-Wformat-nonliteral -Wformat-security -Wmissing-declarations
-Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith
-Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings
-Wno-address-of-packed-member -Wno-packed-not-aligned
-Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC
-march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API
-Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=pmd.vdpa.ifc -MD -MQ
drivers/libtmp_rte_vdpa_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o -MF
drivers/libtmp_rte_vdpa_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o.d -o
drivers/libtmp_rte_vdpa_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o -c
../drivers/vdpa/ifc/ifcvf_vdpa.c
../drivers/vdpa/ifc/ifcvf_vdpa.c: In function ‘vdpa_enable_vfio_intr’:
../drivers/vdpa/ifc/ifcvf_vdpa.c:424:62: error: writing 4 bytes into a region
of size 0 [-Werror=stringop-overflow=]
  424 |                         fd_ptr[RTE_INTR_VEC_RXTX_OFFSET + i] = fd;
      |                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
../drivers/vdpa/ifc/ifcvf_vdpa.c:382:14: note: at offset 32 into destination
object ‘irq_set_buf’ of size 32
  382 |         char irq_set_buf[MSIX_IRQ_SET_BUF_LEN];
      |              ^~~~~~~~~~~
cc1: all warnings being treated as errors
[2516/3588] Compiling C object
drivers/libtmp_rte_crypto_octeontx.a.p/crypto_octeontx_otx_cryptodev_ops.c.o
ninja: build stopped: subcommand failed.

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

             reply	other threads:[~2022-06-20  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  6:10 bugzilla [this message]
2022-06-21  3:23 ` 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-1039-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).