From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 911] [19.11.11-rc1] linux/igb_uio/igb_uiobuild failure with make and clang 13
Date: Fri, 17 Dec 2021 06:46:55 +0000 [thread overview]
Message-ID: <bug-911-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=911
Bug ID: 911
Summary: [19.11.11-rc1] linux/igb_uio/igb_uiobuild failure with
make and clang 13
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: mk
Assignee: dev@dpdk.org
Reporter: yux.jiang@intel.com
Target Milestone: ---
DPDk version:
commit 928100dd6d30e733be411380fdb78c68a061936c (HEAD, tag: v19.11.11-rc1,
origin/19.11)
Author: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Thu Dec 9 15:33:57 2021 +0100
version: 19.11.11-rc1
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
DPDK patch to fix 901/902/903
Verified patchset https://github.com/cpaelzer/dpdk-stable-queue/commits/19.11/
Commit:
net/ixgbe: build failure with make and clang 13
acd0a2d2d net/ice: build failure with make and clang 13
cc089e955 net/i40e: build failure with make and clang 13
TestSteps:
make config MAKE_PAUSE=n O=/tmp/build-x86_64-native-linuxapp-clang
T=x86_64-native-linuxapp-clang
make -j64 MAKE_PAUSE=n O=/tmp/build-x86_64-native-linuxapp-clang
Error Log:
CC ixgbe_mbx.o
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:
In function ‘igbuio_pci_enable_interrupts’:
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:230:20:
error: this statement may fall through [-Werror=implicit-fallthrough=]
230 | if (pci_alloc_irq_vectors(udev->pdev, 1, 1,
PCI_IRQ_MSIX) == 1) {
| ^
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:240:9:
note: here
240 | case RTE_INTR_MODE_MSI:
| ^~~~
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:250:20:
error: this statement may fall through [-Werror=implicit-fallthrough=]
250 | if (pci_alloc_irq_vectors(udev->pdev, 1, 1,
PCI_IRQ_MSI) == 1) {
| ^
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:259:9:
note: here
259 | case RTE_INTR_MODE_LEGACY:
| ^~~~
In file included from ./include/linux/device.h:15,
from
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:8:
./include/linux/dev_printk.h:116:9: error: this statement may fall through
[-Werror=implicit-fallthrough=]
116 | _dev_notice(dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:267:17:
note: in expansion of macro ‘dev_notice’
267 | dev_notice(&udev->pdev->dev, "PCI INTX mask not
supported\n");
| ^~~~~~~~~~
/tmp/build-x86_64-native-linuxapp-clang/build/kernel/linux/igb_uio/igb_uio.c:269:9:
note: here
269 | case RTE_INTR_MODE_NONE:
| ^~~~
CC rte_eth_tap.o
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-12-17 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 6:46 bugzilla [this message]
2021-12-17 7:47 ` 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-911-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).