From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: "Sedat Dilek" <sedat.dilek@gmail.com>,
"Mark Wielaard" <mark@klomp.org>,
"Arnaldo Carvalho de Melo" <arnaldo.melo@gmail.com>,
"Tom Stellard" <tstellar@redhat.com>,
"Jiri Olsa" <jolsa@kernel.org>,
dwarves@vger.kernel.org, bpf <bpf@vger.kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andriin@fb.com>, "Yonghong Song" <yhs@fb.com>,
"Hao Luo" <haoluo@google.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [RFT] pahole 1.20 RC was Re: [PATCH] btf_encoder: Add extra checks for symbol names
Date: Wed, 3 Feb 2021 22:06:29 -0300 [thread overview]
Message-ID: <20210204010629.GB854763@kernel.org> (raw)
In-Reply-To: <CAEf4Bzay-MS9mKc7N9Kc-eQBv1U5DomOY4VoBW=BQZaqs3f0kg@mail.gmail.com>
Em Wed, Feb 03, 2021 at 03:21:58PM -0800, Andrii Nakryiko escreveu:
> On Wed, Feb 3, 2021 at 1:48 PM Sedat Dilek <sedat.dilek@gmail.com> wrote:
> > Looks like CONFIG_DEBUG_INFO_BTF=y makes troubles with LLVM/Clang.
> > Can we have a fix for Linux v5.11-rc6+ to avoid a selection of it when
> > CC_IS_CLANG=y?
> Let's first understand problems and try to fix them, please.
Yeah, from what I've read this is something only related to clang
building the kernel with DWARF5, right?
I just delayed to tomorrow releasing pahole 1.20 as its late here and
there is this discussion going on, what I have is at:
https://git.kernel.org/pub/scm/devel/pahole/pahole.git/log/?h=tmp.1.20
There is one patch more than what I think Sedat tried, that makes a
Mark's patch for DWARF_TAG_call_site{_parameter} to be applied as well
when processing inline expansions, which for what is being discussed
here seems unrelated, just avoids tons of warnings when processing
vmlinux with gcc 11 in fedora rawhide.
- Arnaldo
next prev parent reply other threads:[~2021-02-04 1:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 18:40 [PATCH] btf_encoder: Add extra checks for symbol names Jiri Olsa
2021-01-12 19:20 ` Andrii Nakryiko
2021-01-12 19:47 ` Jiri Olsa
2021-01-12 20:17 ` Sedat Dilek
2021-01-13 0:27 ` Tom Stellard
2021-01-14 7:50 ` Sedat Dilek
2021-01-14 14:33 ` Tom Stellard
2021-01-14 14:39 ` Sedat Dilek
2021-01-21 13:38 ` Arnaldo Carvalho de Melo
2021-01-21 16:06 ` Sedat Dilek
2021-01-21 19:37 ` Arnaldo Carvalho de Melo
2021-01-21 20:53 ` Andrii Nakryiko
2021-01-22 2:07 ` Sedat Dilek
2021-01-22 4:11 ` Andrii Nakryiko
2021-01-28 20:00 ` [RFT] pahole 1.20 RC was " Arnaldo Carvalho de Melo
2021-01-28 20:57 ` Sedat Dilek
2021-01-28 21:11 ` Arnaldo Carvalho de Melo
2021-01-28 22:28 ` Sedat Dilek
2021-02-02 7:48 ` Andrii Nakryiko
2021-02-03 9:03 ` Sedat Dilek
2021-02-03 10:23 ` Mark Wielaard
2021-02-03 21:48 ` Sedat Dilek
2021-02-03 23:21 ` Andrii Nakryiko
2021-02-04 1:06 ` Arnaldo Carvalho de Melo [this message]
2021-02-04 6:40 ` Sedat Dilek
2021-01-21 17:37 ` Tom Stellard
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=20210204010629.GB854763@kernel.org \
--to=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=berrange@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=haoluo@google.com \
--cc=jolsa@kernel.org \
--cc=mark@klomp.org \
--cc=sedat.dilek@gmail.com \
--cc=tstellar@redhat.com \
--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).