From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1096] lib/member build failure with gcc 5.4.0
Date: Mon, 10 Oct 2022 06:59:59 +0000 [thread overview]
Message-ID: <bug-1096-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1096
Bug ID: 1096
Summary: lib/member build failure with gcc 5.4.0
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
$ meson --werror --buildtype=debugoptimized build && ninja -C build
"""
FAILED: lib/member/libsketch_avx512_tmp.a.p/rte_member_sketch_avx512.c.o
[..]
lib/member/rte_member_sketch_avx512.c: In function 'sketch_update_avx512':
lib/member/rte_member_sketch_avx512.c:32:41: error: passing argument 2 of
'_mm512_i32gather_epi64' from incompatible pointer type
[-Werror=incompatible-pointer-types]
_mm512_i32gather_epi64(v_hash_result, count_array, 8);
^
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/include/immintrin.h:45:0,
from lib/member/rte_xxh64_avx512.h:13,
from lib/member/rte_member_sketch_avx512.c:5:
/usr/lib/gcc/x86_64-linux-gnu/5/include/avx512fintrin.h:9331:1: note: expected
'const long long int *' but argument is of type 'uint64_t * {aka long unsigned
int *}'
_mm512_i32gather_epi64 (__m256i __index, long long const *__addr, int __scale)
"""
DPDK: main (de254dac608e)
OS: Ubuntu 16.04.7
Meson: 0.56.2
Ninja: 1.7.1
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-10-10 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 6:59 bugzilla [this message]
2022-10-10 10:40 ` [Bug 1096] lib/member build failure with gcc 5.4.0 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-1096-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.