BPF List
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@fb.com>
To: <sedat.dilek@gmail.com>
Cc: <bpf@vger.kernel.org>, Andrii Nakryiko <andrii@kernel.org>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	<kernel-team@fb.com>, Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH bpf-next v2 0/5] bpf: tools: support build selftests/bpf with clang
Date: Tue, 13 Apr 2021 08:21:51 -0700	[thread overview]
Message-ID: <3996f0de-2ade-ef1a-65c8-fdfb073dfd4d@fb.com> (raw)
In-Reply-To: <CA+icZUVFGe443PsDj8SmBpD95YEBzYATgx8LDQQwYtdY+j6sxw@mail.gmail.com>



On 4/12/21 6:44 PM, Sedat Dilek wrote:
> On Mon, Apr 12, 2021 at 4:29 PM Yonghong Song <yhs@fb.com> wrote:
>>
>> To build kernel with clang, people typically use
>>    make -j60 LLVM=1 LLVM_IAS=1
>> LLVM_IAS=1 is not required for non-LTO build but
>> is required for LTO build. In my environment,
>> I am always having LLVM_IAS=1 regardless of
>> whether LTO is enabled or not.
>>
>> After kernel is build with clang, the following command
>> can be used to build selftests with clang:
>>    make -j60 -C tools/testing/selftests/bpf LLVM=1 LLVM_IAS=1
>>
>> But currently, using the above command, some compilations
>> still use gcc and there are also compilation errors and warnings.
>> This patch set intends to fix these issues.
>> Patch #1 and #2 fixed the issue so clang/clang++ is
>> used instead of gcc/g++. Patch #3 fixed a compilation
>> failure. Patch #4 and #5 fixed various compiler warnings.
>>
> 
> Might be good to add some hints like when the build stops or errors:
> 
> Like in my case when I had no CONFIG_DEBUG_INFO_BTF set.
> 
> Of course in combination with Clang-LTO a pointer "you need pahole
> version 1.21." and CONFIG_DEBUG_INFO_BTF=y.
> 
> Finally, a hint for missing xxx-dev(el) packages (see Nick's report).
> 
> The tools directory has its own build rules thus I cannot say how to
> check for specific Kconfigs.
> I have not looked.

I will add some more information about how I have tested in the
cover letter.

> 
> NOTE: I have not checked without setting CONFIG_DEBUG_INFO.
> 
> - Sedat -
> 
>> Changelog:
>>    v1 -> v2:
>>      . add -Wno-unused-command-line-argument and -Wno-format-security
>>        for clang only as (1). gcc does not exhibit those
>>        warnings, and (2). -Wno-unused-command-line-argument is
>>        only supported by clang. (Sedat)
>>
>> Yonghong Song (5):
>>    selftests: set CC to clang in lib.mk if LLVM is set
>>    tools: allow proper CC/CXX/... override with LLVM=1 in
>>      Makefile.include
>>    selftests/bpf: fix test_cpp compilation failure with clang
>>    selftests/bpf: silence clang compilation warnings
>>    bpftool: fix a clang compilation warning
>>
>>   tools/bpf/bpftool/net.c              |  2 +-
>>   tools/scripts/Makefile.include       | 12 ++++++++++--
>>   tools/testing/selftests/bpf/Makefile |  7 ++++++-
>>   tools/testing/selftests/lib.mk       |  4 ++++
>>   4 files changed, 21 insertions(+), 4 deletions(-)
>>
>> --
>> 2.30.2
>>

  reply	other threads:[~2021-04-13 15:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 14:29 [PATCH bpf-next v2 0/5] bpf: tools: support build selftests/bpf with clang Yonghong Song
2021-04-12 14:29 ` [PATCH bpf-next v2 1/5] selftests: set CC to clang in lib.mk if LLVM is set Yonghong Song
2021-04-12 14:29 ` [PATCH bpf-next v2 2/5] tools: allow proper CC/CXX/... override with LLVM=1 in Makefile.include Yonghong Song
2021-04-12 14:29 ` [PATCH bpf-next v2 3/5] selftests/bpf: fix test_cpp compilation failure with clang Yonghong Song
2021-04-12 14:29 ` [PATCH bpf-next v2 4/5] selftests/bpf: silence clang compilation warnings Yonghong Song
2021-04-13  4:45   ` Andrii Nakryiko
2021-04-12 14:29 ` [PATCH bpf-next v2 5/5] bpftool: fix a clang compilation warning Yonghong Song
2021-04-13  4:48   ` Andrii Nakryiko
2021-04-12 23:58 ` [PATCH bpf-next v2 0/5] bpf: tools: support build selftests/bpf with clang Nick Desaulniers
2021-04-13  0:02   ` Nick Desaulniers
2021-04-13  0:31     ` Yonghong Song
2021-04-13 18:46       ` Nick Desaulniers
2021-04-13 18:56         ` Nick Desaulniers
2021-04-13 20:35           ` Jiri Olsa
2021-04-13 20:45             ` Nick Desaulniers
2021-04-14 13:18               ` Jiri Olsa
2021-04-15  0:16                 ` Andrii Nakryiko
2021-04-15 13:23                   ` Jiri Olsa
2021-04-15 16:55                     ` Nick Desaulniers
2021-04-15 17:17                       ` Jiri Olsa
2021-04-15 21:39                         ` Jiri Olsa
2021-04-13  0:25   ` Yonghong Song
2021-04-13  1:44 ` Sedat Dilek
2021-04-13 15:21   ` Yonghong Song [this message]
2021-04-13  1:50 ` Sedat Dilek

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=3996f0de-2ade-ef1a-65c8-fdfb073dfd4d@fb.com \
    --to=yhs@fb.com \
    --cc=andrii@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=ndesaulniers@google.com \
    --cc=sedat.dilek@gmail.com \
    /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