From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 811] BPF tests fail with clang
Date: Thu, 16 Sep 2021 03:07:41 +0000 [thread overview]
Message-ID: <bug-811-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=811
Bug ID: 811
Summary: BPF tests fail with clang
Product: DPDK
Version: 21.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
The bpf_autotest fails when DPDK 21.11 is built with clang.
Same test and code work when built with Gcc.
$ clang --version
Debian clang version 11.0.1-2
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
$ gcc --version
gcc (Debian 10.2.1-6) 10.2.1 20210110
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ DPDK_TEST='bpf_autotest'
/home/shemminger/DPDK/pcapng2/build/app/test/dpdk-test -l 0-15 --no-huge -m
2048
EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /run/user/1000/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
APP: HPET is not enabled, using TSC as default timer
RTE>>bpf_autotest
run_test(test_store1) start
run_test(test_store2) start
run_test(test_load1) start
run_test(test_ldimm1) start
run_test(test_mul1) start
run_test(test_shift1) start
test_shift1_check: invalid value
expected:
00:80:21:81:00:00:00:00:00:00:00:00:00:00:00:00:ff:db:dd:ed:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:ff:00:00:00:00:00:00:00:00:c0:ed:27:21:00:00:00:00:00:00:00:00:00:00:00:00:81:ef:ad:f6:ff:76:77:fb:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
result:
00:80:21:81:00:00:00:00:00:00:00:00:00:00:00:00:ff:db:dd:ed:ff:ff:ff:ff:00:00:00:00:00:00:00:00:81:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:ff:00:00:00:00:00:00:00:00:c0:ed:27:21:00:00:00:00:00:00:00:00:00:00:00:00:81:ef:ad:f6:ff:76:77:fb:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
run_test@3196: check_result(test_shift1) failed, error: -1(Unknown error -1);
test_shift1_check: invalid value
expected:
00:00:cf:4e:00:00:00:00:00:00:00:00:00:00:00:00:cf:bb:75:ef:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:80:e7:dd:ba:00:00:00:00:00:00:00:00:00:00:00:c0:00:00:00:00:00:00:00:00:00:00:00:00:7b:de:ad:7b:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
result:
00:00:cf:4e:00:00:00:00:00:00:00:00:00:00:00:00:cf:bb:75:ef:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:9e:9d:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:80:e7:dd:ba:00:00:00:00:00:00:00:00:00:00:00:c0:00:00:00:00:00:00:00:00:00:00:00:00:7b:de:ad:7b:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
run_test@3210: check_result(test_shift1) failed, error: -1(Unknown error -1);
run_test(test_jump1) start
run_test(test_jump2) start
run_test(test_alu1) start
run_test(test_bele1) start
run_test(test_xadd1) start
run_test(test_div1) start
bpf_exec(0x7f3a1d03d000): division by 0 at pc: 0x68;
run_test(test_call1) start
run_test(test_call2) start
run_test(test_call3) start
run_test(test_call4) start
run_test(test_call5) start
run_test(test_ld_mbuf1) start
run_test(test_ld_mbuf2) start
run_test(test_ld_mbuf3) start
Test Failed
RTE>>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-09-16 3:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 3:07 bugzilla [this message]
2021-10-16 16:26 ` [dpdk-dev] [Bug 811] BPF tests fail with clang Stephen Hemminger
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-811-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.