From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 697] build failure in event/cnxk when cross-compiling with gcc 7.1.1
Date: Thu, 06 May 2021 11:36:27 +0000 [thread overview]
Message-ID: <bug-697-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=697
Bug ID: 697
Summary: build failure in event/cnxk when cross-compiling with
gcc 7.1.1
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson --werror --buildtype=debugoptimized --cross-file
config/arm/arm64_armv8_linux_gcc build && ninja -C build
...
...
The Meson build system
Version: 0.55.3
Source dir: /tmp/dpdk
Build dir: /tmp/build-aarch64-gcc
Build type: cross build
Program cat found: YES
Project name: DPDK
Project version: 21.05.0-rc2
C compiler for the build machine: ccache cc (gcc 10.3.1 "cc (GCC) 10.3.1
20210422 (Red Hat 10.3.1-1)")
C linker for the build machine: cc ld.bfd 2.35-18
C compiler for the host machine: aarch64-linux-gnu-gcc (gcc 7.1.1
"aarch64-linux-gnu-gcc (Linaro GCC 7.1-2017.08) 7.1.1 20170707")
C linker for the host machine: aarch64-linux-gnu-gcc ld.bfd 2.28.2.20170706
...
...
[2106/2604] Compiling C object
drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker.c.o
FAILED: drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker.c.o
aarch64-linux-gnu-gcc -Idrivers/libtmp_rte_event_cnxk.a.p -Idrivers
-I../dpdk/drivers -Idrivers/event/cnxk -I../dpdk/drivers/event/cnxk
-Ilib/eventdev -I../dpdk/lib/eventdev -I. -I../dpdk -Iconfig -I../dpdk/config
-Ilib/eal/include -I../dpdk/lib/eal/include -Ilib/eal/linux/include
-I../dpdk/lib/eal/linux/include -Ilib/eal/arm/include
-I../dpdk/lib/eal/arm/include -Ilib/eal/common -I../dpdk/lib/eal/common
-Ilib/eal -I../dpdk/lib/eal -Ilib/kvargs -I../dpdk/lib/kvargs -Ilib/metrics
-I../dpdk/lib/metrics -Ilib/telemetry -I../dpdk/lib/telemetry -Ilib/ring
-I../dpdk/lib/ring -Ilib/ethdev -I../dpdk/lib/ethdev -Ilib/net
-I../dpdk/lib/net -Ilib/mbuf -I../dpdk/lib/mbuf -Ilib/mempool
-I../dpdk/lib/mempool -Ilib/meter -I../dpdk/lib/meter -Ilib/hash
-I../dpdk/lib/hash -Ilib/rcu -I../dpdk/lib/rcu -Ilib/timer -I../dpdk/lib/timer
-Ilib/cryptodev -I../dpdk/lib/cryptodev -Idrivers/bus/pci
-I../dpdk/drivers/bus/pci -I../dpdk/drivers/bus/pci/linux -Ilib/pci
-I../dpdk/lib/pci -Idrivers/common/cnxk -I../dpdk/drivers/common/cnxk
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch
-Werror -O2 -g -include rte_config.h -Wextra -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=armv8-a+crc
-DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -MD -MQ
drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker.c.o -MF
drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker.c.o.d -o
drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker.c.o -c
../dpdk/drivers/event/cnxk/cn10k_worker.c
{standard input}: Assembler messages:
{standard input}:620: Error: reg pair must start from even reg at operand 1 --
`caspl x5,x6,x5,x6,[x4]'
[2139/2604] Compiling C object
drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker.c.o
ninja: build stopped: subcommand failed.
"""
os: Fedora 33
cross compiler: gcc 7.1.1 "aarch64-linux-gnu-gcc (Linaro GCC 7.1-2017.08) 7.1.1
20170707"
https://releases.linaro.org/components/toolchain/binaries/7.1-2017.08/aarch64-linux-gnu/gcc-linaro-7.1.1-2017.08-x86_64_aarch64-linux-gnu.tar.xz
meson: 0.55.3
ninja: 1.10.2
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-05-06 11:36 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-697-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.