DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1159] lib/vhost build failure with clang 3.4.2
Date: Sat, 11 Feb 2023 13:46:19 +0000	[thread overview]
Message-ID: <bug-1159-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1159
           Summary: lib/vhost build failure with clang 3.4.2
           Product: DPDK
           Version: 23.03
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: vhost/virtio
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

```
FAILED: lib/librte_vhost.a.p/vhost_iotlb.c.o
clang -Ilib/librte_vhost.a.p -Ilib -I../../root/dpdk/lib -Ilib/vhost
-I../../root/dpdk/lib/vhost -I. -I../../root/dpdk -Iconfig
-I../../root/dpdk/config -Ilib/eal/include -I../../root/dpdk/lib/eal/include
-Ilib/eal/linux/include -I../../root/dpdk/lib/eal/linux/include
-Ilib/eal/x86/include -I../../root/dpdk/lib/eal/x86/include -Ilib/eal/common
-I../../root/dpdk/lib/eal/common -Ilib/eal -I../../root/dpdk/lib/eal
-Ilib/kvargs -I../../root/dpdk/lib/kvargs -Ilib/metrics
-I../../root/dpdk/lib/metrics -Ilib/telemetry -I../../root/dpdk/lib/telemetry
-Ilib/ethdev -I../../root/dpdk/lib/ethdev -Ilib/net -I../../root/dpdk/lib/net
-Ilib/mbuf -I../../root/dpdk/lib/mbuf -Ilib/mempool
-I../../root/dpdk/lib/mempool -Ilib/ring -I../../root/dpdk/lib/ring -Ilib/meter
-I../../root/dpdk/lib/meter -Ilib/cryptodev -I../../root/dpdk/lib/cryptodev
-Ilib/rcu -I../../root/dpdk/lib/rcu -Ilib/hash -I../../root/dpdk/lib/hash
-Ilib/pci -I../../root/dpdk/lib/pci -Ilib/dmadev -I../../root/dpdk/lib/dmadev
-Xclang -fcolor-diagnostics -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch
-Wextra -Werror -O2 -g -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-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -mno-avx512f
-mno-avx512f -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -fno-strict-aliasing
-DRTE_LOG_DEFAULT_LOGTYPE=lib.vhost -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD
-MQ lib/librte_vhost.a.p/vhost_iotlb.c.o -MF
lib/librte_vhost.a.p/vhost_iotlb.c.o.d -o lib/librte_vhost.a.p/vhost_iotlb.c.o
-c ../../root/dpdk/lib/vhost/iotlb.c
In file included from ../../root/dpdk/lib/vhost/iotlb.c:11:
In file included from ../../root/dpdk/lib/vhost/iotlb.h:10:
../../root/dpdk/lib/vhost/vhost.h:518:2: error: GCC does not allow
assert_exclusive_lock attribute in this position on a function definition
[-Werror,-Wgcc-compat]
        __rte_assert_exclusive_lock(&vq->access_lock)
        ^
../../root/dpdk/lib/eal/include/rte_lock_annotations.h:29:38: note: expanded
from macro '__rte_assert_exclusive_lock'
        __attribute__((assert_exclusive_lock(__VA_ARGS__)))
                                            ^
1 error generated.
```

OS: CentOS Linux 7
clang: 3.4.2

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

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

             reply	other threads:[~2023-02-11 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 13:46 bugzilla [this message]
2023-02-20  7:29 ` 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-1159-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).