DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 907] [19.11] build failure Werror=implicit-fallthrough in opensuse tumbleweed
Date: Tue, 14 Dec 2021 14:04:59 +0000	[thread overview]
Message-ID: <bug-907-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 907
           Summary: [19.11] build failure Werror=implicit-fallthrough in
                    opensuse tumbleweed
           Product: DPDK
           Version: 19.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: christian.ehrhardt@canonical.com
  Target Milestone: ---

Build in opensuse_tumbleweed fails with newer gcc complaining about implicit
fallthrough.


[  116s]
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:
In function 'igbuio_pci_enable_interrupts':
[  116s]
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:230:20:
error: this statement may fall through [-Werror=implicit-fallthrough=]
[  116s]   230 |                 if (pci_alloc_irq_vectors(udev->pdev, 1, 1,
PCI_IRQ_MSIX) == 1) {
[  116s]       |                    ^
[  116s]
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:240:9:
note: here
[  116s]   240 |         case RTE_INTR_MODE_MSI:
[  116s]       |         ^~~~
[  116s]
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:250:20:
error: this statement may fall through [-Werror=implicit-fallthrough=]
[  116s]   250 |                 if (pci_alloc_irq_vectors(udev->pdev, 1, 1,
PCI_IRQ_MSI) == 1) {
[  116s]       |                    ^
[  116s]
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:259:9:
note: here
[  116s]   259 |         case RTE_INTR_MODE_LEGACY:
[  116s]       |         ^~~~
[  116s] In file included from
/usr/src/linux-5.15.7-1/include/linux/device.h:15,
[  116s]                  from
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:8:
[  116s] /usr/src/linux-5.15.7-1/include/linux/dev_printk.h:148:31: error: this
statement may fall through [-Werror=implicit-fallthrough=]
[  116s]   148 |         dev_printk_index_wrap(_dev_notice, KERN_NOTICE, dev,
dev_fmt(fmt), ##__VA_ARGS__)
[  116s]       |                               ^
[  116s] /usr/src/linux-5.15.7-1/include/linux/dev_printk.h:110:17: note: in
definition of macro 'dev_printk_index_wrap'
[  116s]   110 |                 _p_func(dev, fmt, ##__VA_ARGS__);             
         \
[  116s]       |                 ^~~~~~~
[  116s]
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:267:17:
note: in expansion of macro 'dev_notice'
[  116s]   267 |                 dev_notice(&udev->pdev->dev, "PCI INTX mask
not supported\n");
[  116s]       |                 ^~~~~~~~~~
[  116s]
/home/abuild/rpmbuild/BUILD/dpdk-1639465174.d43fa3e19/x86_64-default-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:269:9:
note: here
[  116s]   269 |         case RTE_INTR_MODE_NONE:
[  116s]       |         ^~~~

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

                 reply	other threads:[~2021-12-14 14:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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