From: patchwork-bot+netdevbpf@kernel.org
To: Andrew Delgadillo <adelg@google.com>
Cc: yhs@fb.com, bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf-next v3] selftests/bpf: Drop the need for LLVM's llc
Date: Fri, 11 Dec 2020 06:10:06 +0000 [thread overview]
Message-ID: <160766700661.11568.14135729459303174794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201211004344.3355074-1-adelg@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 11 Dec 2020 00:43:44 +0000 you wrote:
> LLC is meant for compiler development and debugging. Consequently, it
> exposes many low level options about its backend. To avoid future bugs
> introduced by using the raw LLC tool, use clang directly so that all
> appropriate options are passed to the back end.
>
> Additionally, simplify the Makefile by removing the
> CLANG_NATIVE_BPF_BUILD_RULE as it is not being use, stop passing
> dwarfris attr since elfutils/libdw now supports the bpf backend (which
> should work with any recent pahole), and stop passing alu32 since
> -mcpu=v3 implies alu32.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] selftests/bpf: Drop the need for LLVM's llc
https://git.kernel.org/bpf/bpf-next/c/89ad7420b25c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-11 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 20:53 [PATCH bpf-next] selftests/bpf: Drop the need for LLVM's llc Andrew Delgadillo
2020-12-10 2:16 ` Yonghong Song
2020-12-10 17:12 ` Andrew Delgadillo
2020-12-10 19:41 ` [PATCH bpf-next v2] " Andrew Delgadillo
2020-12-10 19:41 ` Andrew Delgadillo
2020-12-10 23:55 ` Yonghong Song
2020-12-11 0:43 ` [PATCH bpf-next v3] " Andrew Delgadillo
2020-12-11 1:26 ` Yonghong Song
2020-12-11 6:10 ` patchwork-bot+netdevbpf [this message]
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=160766700661.11568.14135729459303174794.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adelg@google.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=yhs@fb.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