From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: mattias.ronnblom@ericsson.com, robot@bytheb.org
Subject: |FAILURE| pw140559 [RFC v3 5/5] eal: provide option to use compiler memcpy instead of RTE
Date: Sun, 2 Jun 2024 09:43:47 -0400 [thread overview]
Message-ID: <20240602134347.2124348-1-robot@bytheb.org> (raw)
In-Reply-To: <20240602123921.363625-6-mattias.ronnblom@ericsson.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/140559/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9338503481
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-static-i386" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-static-i386" at step Build and test
####################################################################################
[1161/3202] Linking static target drivers/net/fm10k/base/libfm10k_base.a.
[1162/3202] Compiling C object 'drivers/a715181@@tmp_rte_net_failsafe@sta/net_failsafe_failsafe_ops.c.o'.
[1163/3202] Linking static target drivers/libtmp_rte_net_failsafe.a.
[1164/3202] Generating rte_net_failsafe.pmd.c with a custom command.
[1165/3202] Compiling C object 'drivers/a715181@@rte_net_failsafe@sta/meson-generated_.._rte_net_failsafe.pmd.c.o'.
[1166/3202] Linking static target drivers/librte_net_failsafe.a.
[1167/3202] Compiling C object 'drivers/a715181@@rte_net_failsafe@sha/meson-generated_.._rte_net_failsafe.pmd.c.o'.
[1168/3202] Linking target drivers/librte_net_failsafe.so.24.2.
[1169/3202] Compiling C object 'drivers/a715181@@tmp_rte_net_fm10k@sta/net_fm10k_fm10k_rxtx_vec.c.o'.
FAILED: drivers/a715181@@tmp_rte_net_fm10k@sta/net_fm10k_fm10k_rxtx_vec.c.o
ccache gcc -Idrivers/a715181@@tmp_rte_net_fm10k@sta -Idrivers -I../drivers -Idrivers/net/fm10k -I../drivers/net/fm10k -Idrivers/net/fm10k/base -I../drivers/net/fm10k/base -Ilib/ethdev -I../lib/ethdev -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -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-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -Wno-pointer-to-int-cast -D_GNU_SOURCE -m32 -fPIC -march=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.fm10k -MD -MQ 'drivers/a715181@@tmp_rte_net_fm10k@sta/net_fm10k_fm10k_rxtx_vec.c.o' -MF 'drivers/a715181@@tmp_rte_net_fm10k@sta/net_fm10k_fm10k_rxtx_vec.c.o.d' -o 'drivers/a715181@@tmp_rte_net_fm10k@sta/net_fm10k_fm10k_rxtx_vec.c.o' -c ../drivers/net/fm10k/fm10k_rxtx_vec.c
../drivers/net/fm10k/fm10k_rxtx_vec.c: In function ‘fm10k_desc_to_olflags_v’:
../drivers/net/fm10k/fm10k_rxtx_vec.c:131:21: error: implicit declaration of function ‘_mm_cvtsi128_si64’; did you mean ‘_mm_cvtsi128_si32’? [-Werror=implicit-function-declaration]
131 | vol.dword = _mm_cvtsi128_si64(vtag1);
| ^~~~~~~~~~~~~~~~~
| _mm_cvtsi128_si32
../drivers/net/fm10k/fm10k_rxtx_vec.c:131:21: error: nested extern declaration of ‘_mm_cvtsi128_si64’ [-Werror=nested-externs]
cc1: all warnings being treated as errors
[1170/3202] Compiling C object 'drivers/a715181@@tmp_rte_net_fm10k@sta/net_fm10k_fm10k_rxtx.c.o'.
[1171/3202] Compiling C object 'drivers/a715181@@tmp_rte_net_gve@sta/net_gve_base_gve_adminq.c.o'.
[1172/3202] Compiling C object 'drivers/a715181@@tmp_rte_net_fm10k@sta/net_fm10k_fm10k_ethdev.c.o'.
[1173/3202] Compiling C object 'drivers/a715181@@tmp_rte_net_gve@sta/net_gve_gve_rx_dqo.c.o'.
[1174/3202] Compiling C object 'drivers/a715181@@tmp_rte_net_gve@sta/net_gve_gve_rx.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-static-i386" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-06-02 13:43 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240602123921.363625-6-mattias.ronnblom@ericsson.com>
2024-06-02 12:24 ` |SUCCESS| pw140555-140559 " qemudev
2024-06-02 12:29 ` qemudev
2024-06-02 12:51 ` |SUCCESS| pw140559 " checkpatch
2024-06-02 13:27 ` |SUCCESS| pw140555-140559 [PATCH] [RFC,v3,5/5] eal: provide option t dpdklab
2024-06-02 13:27 ` dpdklab
2024-06-02 13:27 ` dpdklab
2024-06-02 13:27 ` dpdklab
2024-06-02 13:27 ` dpdklab
2024-06-02 13:28 ` dpdklab
2024-06-02 13:28 ` dpdklab
2024-06-02 13:28 ` dpdklab
2024-06-02 13:28 ` dpdklab
2024-06-02 13:29 ` dpdklab
2024-06-02 13:29 ` dpdklab
2024-06-02 13:29 ` dpdklab
2024-06-02 13:29 ` dpdklab
2024-06-02 13:30 ` dpdklab
2024-06-02 13:32 ` dpdklab
2024-06-02 13:33 ` dpdklab
2024-06-02 13:33 ` dpdklab
2024-06-02 13:34 ` dpdklab
2024-06-02 13:34 ` dpdklab
2024-06-02 13:37 ` dpdklab
2024-06-02 13:37 ` dpdklab
2024-06-02 13:37 ` dpdklab
2024-06-02 13:38 ` dpdklab
2024-06-02 13:39 ` dpdklab
2024-06-02 13:40 ` dpdklab
2024-06-02 13:40 ` dpdklab
2024-06-02 13:42 ` dpdklab
2024-06-02 13:43 ` dpdklab
2024-06-02 13:43 ` 0-day Robot [this message]
2024-06-02 13:44 ` dpdklab
2024-06-02 13:44 ` dpdklab
2024-06-02 13:44 ` dpdklab
2024-06-02 13:45 ` dpdklab
2024-06-02 13:46 ` dpdklab
2024-06-02 13:46 ` dpdklab
2024-06-02 13:46 ` dpdklab
2024-06-02 13:48 ` dpdklab
2024-06-02 13:49 ` dpdklab
2024-06-02 13:49 ` dpdklab
2024-06-02 13:51 ` dpdklab
2024-06-02 13:55 ` dpdklab
2024-06-02 13:57 ` dpdklab
2024-06-02 13:58 ` dpdklab
2024-06-02 13:59 ` dpdklab
2024-06-02 14:00 ` dpdklab
2024-06-02 14:00 ` dpdklab
2024-06-02 14:00 ` dpdklab
2024-06-02 14:02 ` dpdklab
2024-06-02 14:02 ` dpdklab
2024-06-02 14:03 ` dpdklab
2024-06-02 14:04 ` dpdklab
2024-06-02 14:04 ` dpdklab
2024-06-02 14:10 ` dpdklab
2024-06-02 14:12 ` dpdklab
2024-06-02 14:12 ` dpdklab
2024-06-02 14:13 ` dpdklab
2024-06-02 14:14 ` dpdklab
2024-06-02 14:15 ` dpdklab
2024-06-02 14:15 ` dpdklab
2024-06-02 14:15 ` dpdklab
2024-06-02 14:33 ` dpdklab
2024-06-02 14:33 ` dpdklab
2024-06-02 14:34 ` dpdklab
2024-06-02 14:34 ` dpdklab
2024-06-02 14:35 ` dpdklab
2024-06-02 14:35 ` dpdklab
2024-06-02 14:36 ` dpdklab
2024-06-02 14:36 ` dpdklab
2024-06-02 14:37 ` dpdklab
2024-06-02 14:40 ` dpdklab
2024-06-02 14:40 ` dpdklab
2024-06-02 14:41 ` dpdklab
2024-06-02 14:41 ` dpdklab
2024-06-02 14:42 ` dpdklab
2024-06-02 14:47 ` dpdklab
2024-06-02 14:52 ` dpdklab
2024-06-02 14:53 ` dpdklab
2024-06-02 14:54 ` dpdklab
2024-06-02 14:56 ` dpdklab
2024-06-02 15:01 ` dpdklab
2024-06-02 15:03 ` dpdklab
2024-06-02 15:07 ` dpdklab
2024-06-02 15:08 ` dpdklab
2024-06-02 15:11 ` dpdklab
2024-06-02 15:15 ` dpdklab
2024-06-02 15:22 ` dpdklab
2024-06-02 15:30 ` dpdklab
2024-06-02 16:06 ` dpdklab
2024-06-02 16:27 ` dpdklab
2024-06-02 16:31 ` dpdklab
2024-06-02 16:47 ` dpdklab
2024-06-02 17:31 ` dpdklab
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=20240602134347.2124348-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=mattias.ronnblom@ericsson.com \
--cc=test-report@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).