From: patchwork-bot+bpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, andriin@fb.com
Subject: Re: [PATCH bpf-next v2 1/2] samples/bpf: change Makefile to cope with latest llvm
Date: Tue, 06 Oct 2020 18:50:04 +0000 [thread overview]
Message-ID: <160201020454.15578.6708342423327646865.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201006043427.1891742-1-yhs@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Mon, 5 Oct 2020 21:34:26 -0700 you wrote:
> With latest llvm trunk, bpf programs under samples/bpf
> directory, if using CORE, may experience the following
> errors:
>
> LLVM ERROR: Cannot select: intrinsic %llvm.preserve.struct.access.index
> PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace.
> Stack dump:
> 0. Program arguments: llc -march=bpf -filetype=obj -o samples/bpf/test_probe_write_user_kern.o
> 1. Running pass 'Function Pass Manager' on module '<stdin>'.
> 2. Running pass 'BPF DAG->DAG Pattern Instruction Selection' on function '@bpf_prog1'
> #0 0x000000000183c26c llvm::sys::PrintStackTrace(llvm::raw_ostream&, int)
> (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x183c26c)
> ...
> #7 0x00000000017c375e (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x17c375e)
> #8 0x00000000016a75c5 llvm::SelectionDAGISel::CannotYetSelect(llvm::SDNode*)
> (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x16a75c5)
> #9 0x00000000016ab4f8 llvm::SelectionDAGISel::SelectCodeCommon(llvm::SDNode*, unsigned char const*,
> unsigned int) (/data/users/yhs/work/llvm-project/llvm/build.cur/install/bin/llc+0x16ab4f8)
> ...
> Aborted (core dumped) | llc -march=bpf -filetype=obj -o samples/bpf/test_probe_write_user_kern.o
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] samples/bpf: change Makefile to cope with latest llvm
https://git.kernel.org/bpf/bpf-next/c/9618bde489b2
- [bpf-next,v2,2/2] samples/bpf: fix a compilation error with fallthrough marking
https://git.kernel.org/bpf/bpf-next/c/544d6adf3c3d
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-10-06 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 4:34 [PATCH bpf-next v2 1/2] samples/bpf: change Makefile to cope with latest llvm Yonghong Song
2020-10-06 4:34 ` [PATCH bpf-next v2 2/2] samples/bpf: fix a compilation error with fallthrough marking Yonghong Song
2020-10-06 18:50 ` patchwork-bot+bpf [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=160201020454.15578.6708342423327646865.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bpf@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).