From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: fengchengwen@huawei.com, robot@bytheb.org
Subject: |FAILURE| pw139220 [PATCH] ethdev: fix strict aliasing lead to link cannot be up
Date: Thu, 11 Apr 2024 00:04:13 -0400 [thread overview]
Message-ID: <20240411040413.2733483-1-robot@bytheb.org> (raw)
In-Reply-To: <20240411030749.41874-1-fengchengwen@huawei.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/139220/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8641083568
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-clang-stdatomic" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
ccache clang -Ilib/76b5a35@@rte_ethdev@sta -Ilib -I../lib -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 -Xclang -fcolor-diagnostics -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-missing-field-initializers -D_GNU_SOURCE -fPIC -march=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -DRTE_FLOW_DEBUG -DRTE_LOG_DEFAULT_LOGTYPE=lib.ethdev -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ 'lib/76b5a35@@rte_ethdev@sta/ethdev_rte_ethdev.c.o' -MF 'lib/76b5a35@@rte_ethdev@sta/ethdev_rte_ethdev.c.o.d' -o 'lib/76b5a35@@rte_ethdev@sta/ethdev_rte_ethdev.c.o' -c ../lib/ethdev/rte_ethdev.c
In file included from ../lib/ethdev/rte_ethdev.c:32:
../lib/ethdev/ethdev_driver.h:1679:19: error: address argument to atomic operation must be a pointer to _Atomic type ('uint64_t *' (aka 'unsigned long *') invalid)
old_link.val64 = rte_atomic_exchange_explicit(&dev->data->dev_link.val64,
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_stdatomic.h:79:2: note: expanded from macro 'rte_atomic_exchange_explicit'
atomic_exchange_explicit(ptr, val, memorder)
^ ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:133:34: note: expanded from macro 'atomic_exchange_explicit'
#define atomic_exchange_explicit __c11_atomic_exchange
^
In file included from ../lib/ethdev/rte_ethdev.c:32:
../lib/ethdev/ethdev_driver.h:1699:16: error: address argument to atomic operation must be a pointer to _Atomic type ('uint64_t *' (aka 'unsigned long *') invalid)
link->val64 = rte_atomic_load_explicit(&dev->data->dev_link.val64,
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_stdatomic.h:73:2: note: expanded from macro 'rte_atomic_load_explicit'
atomic_load_explicit(ptr, memorder)
^ ~~~
/usr/lib/llvm-14/lib/clang/14.0.0/include/stdatomic.h:130:30: note: expanded from macro 'atomic_load_explicit'
#define atomic_load_explicit __c11_atomic_load
^
2 errors generated.
[72/2954] Compiling C object 'lib/76b5a35@@rte_eal@sta/eal_unix_rte_thread.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-04-11 4:04 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240411030749.41874-1-fengchengwen@huawei.com>
2024-04-11 3:01 ` |SUCCESS| " qemudev
2024-04-11 3:05 ` qemudev
2024-04-11 3:11 ` checkpatch
2024-04-11 3:44 ` |SUCCESS| pw139220 [PATCH] ethdev: fix strict aliasing lead to link dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:45 ` dpdklab
2024-04-11 3:46 ` dpdklab
2024-04-11 3:48 ` dpdklab
2024-04-11 3:48 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:49 ` dpdklab
2024-04-11 3:50 ` dpdklab
2024-04-11 3:50 ` dpdklab
2024-04-11 3:50 ` dpdklab
2024-04-11 3:53 ` dpdklab
2024-04-11 3:54 ` dpdklab
2024-04-11 3:55 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:56 ` dpdklab
2024-04-11 3:57 ` dpdklab
2024-04-11 3:58 ` dpdklab
2024-04-11 3:58 ` dpdklab
2024-04-11 3:59 ` dpdklab
2024-04-11 3:59 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:00 ` dpdklab
2024-04-11 4:04 ` 0-day Robot [this message]
2024-04-11 4:23 ` dpdklab
2024-04-11 4:23 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:24 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:25 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:26 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:27 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:28 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:30 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:31 ` dpdklab
2024-04-11 4:37 ` dpdklab
2024-04-11 4:38 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:39 ` dpdklab
2024-04-11 4:40 ` dpdklab
2024-04-11 4:48 ` dpdklab
2024-04-11 5:03 ` dpdklab
2024-04-11 5:16 ` dpdklab
2024-04-11 5:16 ` dpdklab
2024-04-11 5:17 ` dpdklab
2024-04-11 5:17 ` dpdklab
2024-04-11 5:18 ` dpdklab
2024-04-11 5:19 ` dpdklab
2024-04-11 5:23 ` dpdklab
2024-04-11 5:24 ` dpdklab
2024-04-11 5:27 ` dpdklab
2024-04-11 5:29 ` dpdklab
2024-04-11 5:31 ` dpdklab
2024-04-11 5:34 ` dpdklab
2024-04-11 5:35 ` dpdklab
2024-04-11 5:36 ` dpdklab
2024-04-11 5:41 ` dpdklab
2024-04-11 5:48 ` dpdklab
2024-04-11 6:04 ` dpdklab
2024-04-11 6:08 ` dpdklab
2024-04-11 6:12 ` dpdklab
2024-04-11 6:13 ` 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=20240411040413.2733483-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=fengchengwen@huawei.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).