DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Qiming Yang <qiming.yang@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>
Subject: [dpdk-dev] dpdk-next-net build is broken because of avx512
Date: Mon, 26 Oct 2020 19:40:35 +0300	[thread overview]
Message-ID: <7549340b-b4ab-8e19-cfc3-dca1a790197e@oktetlabs.ru> (raw)

Hi,

Is it a known issue that dpdk-next-net build is broken on Ubuntu 18.04?

gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0

FAILED: drivers/net/ice/libice_avx512_lib.a.p/ice_rxtx_vec_avx512.c.o
*c*c -Idrivers/net/ice/libice_avx512_lib.a.p -Idrivers/net/ice -I../drivers/net/ice -Idrivers/net/ice/base -I../drivers/net/ice/base -Idrivers/common/iavf -I../drivers/common/iavf -Ilib/librte_ethdev -I../lib/librte_ethdev -I. -I.. -Iconfig -I../config -Ilib/librte_eal/include -I../lib/librte_eal/include -Ilib/librte_eal/linux/include -I../lib/librte_eal/linux/include -Ilib/librte_eal/x86/include -I../lib/librte_eal/x86/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_metrics -I../lib/librte_metrics -Ilib/librte_telemetry -I../lib/librte_telemetry -Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_meter -I../lib/librte_meter -Ilib/librte_hash -I../lib/librte_hash -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O3 -include rte_config.h -Wextra -Wcast-qual -Wdeprecated -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 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DCC_AVX512_SUPPORT -march=skylake-avx512 -mavx512f -MD -MQ drivers/net/ice/libice_avx512_lib.a.p/ice_rxtx_vec_avx512.c.o -MF drivers/net/ice/libice_avx512_lib.a.p/ice_rxtx_vec_avx512.c.o.d -o drivers/net/ice/libice_avx512_lib.a.p/ice_rxtx_vec_avx512.c.o -c ../drivers/net/ice/ice_rxtx_vec_avx512.c
In file included from /usr/lib/gcc/x86_64-linux-gnu/7/include/immintrin.h:55:0,
from /usr/lib/gcc/x86_64-linux-gnu/7/include/x86intrin.h:48,
*f*rom ../lib/librte_eal/x86/include/rte_vect.h:31,
*f*rom ../lib/librte_eal/x86/include/rte_memcpy.h:17,
from ../lib/librte_net/rte_ether.h:21,
from ../lib/librte_ethdev/rte_ethdev.h:159,
from ../lib/librte_ethdev/rte_ethdev_driver.h:18,
from ../drivers/net/ice/ice_ethdev.h:10,
from ../drivers/net/ice/ice_rxtx.h:8,
from ../drivers/net/ice/ice_rxtx_vec_common.h:8,
from ../drivers/net/ice/ice_rxtx_vec_avx512.c:5:
../drivers/net/ice/ice_rxtx_vec_avx512.c: In function ‘ice_rxq_rearm’:
/usr/lib/gcc/x86_64-linux-gnu/7/include/avx512bwintrin.h:3089:1: error: inlining failed in call to always_inline ‘_mm512_bsrli_epi128’: target specific option mismatch
_mm512_bsrli_epi128 (__m512i __A, const int __N)
^~~~~~~~~~~~~~~~~~~
*.*/drivers/net/ice/ice_rxtx_vec_avx512.c:97:17: note: called from here
const __m512i desc6_7 = _mm512_bsrli_epi128(desc4_5, 8);
^~~~~~~

clang version 6.0.0-1ubuntu2 build is OK on the same host/OS.

Andrew.


             reply	other threads:[~2020-10-26 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 16:40 Andrew Rybchenko [this message]
2020-10-27  8:47 ` David Marchand

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=7549340b-b4ab-8e19-cfc3-dca1a790197e@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=thomas@monjalon.net \
    /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).