From: Prabhakar Kushwaha <prabhakar.pkin@gmail.com>
To: Yonghong Song <yhs@fb.com>
Cc: "ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: Linux-5.4: bpf: test_core_reloc_arrays.o: Segmentation fault with llc -march=bpf
Date: Wed, 23 Oct 2019 14:19:53 +0530 [thread overview]
Message-ID: <CAJ2QiJKqU5GDNa4YHggboy4YUJHB_rr6x_dXWy0hK+jD5Sv29g@mail.gmail.com> (raw)
In-Reply-To: <c854894e-6c0a-6d49-4d7f-ae81a34b5711@fb.com>
On Wed, Oct 23, 2019 at 10:12 AM Yonghong Song <yhs@fb.com> wrote:
>
>
>
> On 10/22/19 8:29 PM, Prabhakar Kushwaha wrote:
> > Thanks Yonghong for replying.
> >
> >
> >
> > On Wed, Oct 23, 2019 at 8:04 AM Yonghong Song <yhs@fb.com> wrote:
> >>
> >>
> >>
> >> On 10/22/19 6:35 PM, Prabhakar Kushwaha wrote:
> >>>
> >>> Adding other mailing list, folks...
> >>>
> >>> Hi All,
> >>>
> >>> I am trying to build kselftest on Linux-5.4 on ubuntu 18.04. I installed
> >>> LLVM-9.0.0 and Clang-9.0.0 from below links after following steps from
> >>> [1] because of discussion [2]
> >>
> >> Could you try latest llvm trunk (pre-release 10.0.0)?
> >> LLVM 9.0.0 has some codes for CORE, but it is not fully supported and
> >> has some bugs which are only fixed in LLVM 10.0.0. We intend to make
> >> llvm 10 as the one we claim we have support. Indeed CORE related
> >> changes are mostly added during 10.0.0 development period.
> >>
> >
> > can you please help me the link to download as
> > "https://urldefense.proofpoint.com/v2/url?u=https-3A__prereleases.llvm.org_&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=DA8e1B5r073vIqRrFz7MRA&m=-6k0f7iKZO54kHLKBjYdU_7pDlCh61HdtyWQ-d43zwU&s=7fbobFiC619_9Pr5b1FbrKvoHl6sg79NZc3rQgNWa1Q&e= " does not have LLVM-10.0.0 packages.
>
> llvm 10 has not been released.
> Could you follow LLVM source build insn at
> https://github.com/iovisor/bcc/blob/master/INSTALL.md?
>
> Specifically:
> git clone http://llvm.org/git/llvm.git
> cd llvm/tools; git clone http://llvm.org/git/clang.git
> cd ..; mkdir -p build/install; cd build
> cmake -G "Unix Makefiles" -DLLVM_TARGETS_TO_BUILD="BPF;X86" \
> -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$PWD/install ..
> make
> make install
> export PATH=$PWD/install/bin:$PATH
>
Thanks Yonghong..
after following above steps no more segmentation fault are there.
--pk
next prev parent reply other threads:[~2019-10-23 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 1:35 Linux-5.4: bpf: test_core_reloc_arrays.o: Segmentation fault with llc -march=bpf Prabhakar Kushwaha
2019-10-23 2:34 ` Yonghong Song
2019-10-23 3:29 ` Prabhakar Kushwaha
2019-10-23 4:42 ` Yonghong Song
2019-10-23 8:49 ` Prabhakar Kushwaha [this message]
2019-10-24 16:04 ` Ilya Leoshkevich
2019-10-24 17:49 ` Yonghong Song
2019-10-24 18:31 ` Ilya Leoshkevich
2019-10-25 21:50 ` Yonghong Song
-- strict thread matches above, loose matches on Subject: below --
2019-10-22 14:12 Prabhakar Kushwaha
2019-10-20 13:47 Prabhakar Kushwaha
2019-10-21 3:50 ` Prabhakar Kushwaha
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=CAJ2QiJKqU5GDNa4YHggboy4YUJHB_rr6x_dXWy0hK+jD5Sv29g@mail.gmail.com \
--to=prabhakar.pkin@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kselftest@vger.kernel.org \
--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).