-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
selftests/bpf: workarounds for GCC BPF build #8310
Conversation
Upstream branch: 96ea081 |
2db328a
to
716c9e0
Compare
Upstream branch: 73b9075 |
0b41735
to
546d30a
Compare
716c9e0
to
c1d981b
Compare
Upstream branch: 8c21f88 |
546d30a
to
116f6c9
Compare
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=922166 expired. Closing PR. |
Upstream branch: 2532608 |
116f6c9
to
b38b9a9
Compare
b58ecc3
to
5c57fa7
Compare
Various compilation errors happen when BPF programs in selftests/bpf are built with GCC BPF. For more details see the discussion at [1]. The changes only affect test_progs-bpf_gcc, which is built only if BPF_GCC is set: * Pass -std=gnu17 to gcc in order to avoid errors on bool types declarations in vmlinux.h * Pass -fno-strict-aliasing for tests that trigger uninitialized variable warning on BPF_RAW_INSNS [2] [1] https://lore.kernel.org/bpf/EYcXjcKDCJY7Yb0GGtAAb7nLKPEvrgWdvWpuNzXm2qi6rYMZDixKv5KwfVVMBq17V55xyC-A1wIjrqG3aw-Imqudo9q9X7D7nLU2gWgbN0w=@pm.me/ [2] https://lore.kernel.org/bpf/[email protected]/ CC: Jose E. Marchesi <[email protected]> Signed-off-by: Ihor Solodrai <[email protected]>
Upstream branch: 859a7db |
b38b9a9
to
70b5085
Compare
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=922659 expired. Closing PR. |
Pull request for series with
subject: selftests/bpf: workarounds for GCC BPF build
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=922166