From: Yonghong Song <yhs@fb.com>
To: Nick Desaulniers <ndesaulniers@google.com>,
Sedat Dilek <sedat.dilek@gmail.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Clang-Built-Linux ML <clang-built-linux@googlegroups.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Jakub Jelinek <jakub@redhat.com>,
Fangrui Song <maskray@google.com>,
Caroline Tice <cmtice@google.com>,
Nick Clifton <nickc@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH v5 0/3] Kbuild: DWARF v5 support
Date: Fri, 15 Jan 2021 15:43:06 -0800 [thread overview]
Message-ID: <12b6c2ca-4cf7-4edd-faf2-72e3cb59c00e@fb.com> (raw)
In-Reply-To: <CAKwvOd=5iR0JONwDb6ypD7dzzjOS3Uj0CjcyYqPF48eK4Pi90Q@mail.gmail.com>
On 1/15/21 3:34 PM, Nick Desaulniers wrote:
> On Fri, Jan 15, 2021 at 3:24 PM Yonghong Song <yhs@fb.com> wrote:
>>
>>
>>
>> On 1/15/21 1:53 PM, Sedat Dilek wrote:
>>> En plus, I encountered breakage with GCC v10.2.1 and LLVM=1 and
>>> CONFIG_DEBUG_INFO_DWARF4.
>>> So might be good to add a "depends on !DEBUG_INFO_BTF" in this combination.
>
> Can you privately send me your configs that repro? Maybe I can isolate
> it to a set of configs?
>
>>
>> I suggested not to add !DEBUG_INFO_BTF to CONFIG_DEBUG_INFO_DWARF4.
>> It is not there before and adding this may suddenly break some users.
>>
>> If certain combination of gcc/llvm does not work for
>> CONFIG_DEBUG_INFO_DWARF4 with pahole, this is a bug bpf community
>> should fix.
>
> Is there a place I should report bugs?
You can send bug report to Arnaldo Carvalho de Melo <acme@kernel.org>,
dwarves@vger.kernel.org and bpf@vger.kernel.org.
>
>>
>>>
>>> I had some other small nits commented in the single patches.
>>>
>>> As requested in your previous patch-series, feel free to add my:
>>>
>>> Tested-by: Sedat Dilek <sedat.dilek@gmail.com>
>
> Yeah, I'll keep it if v6 is just commit message changes.
>
next prev parent reply other threads:[~2021-01-15 23:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 21:06 [PATCH v5 0/3] Kbuild: DWARF v5 support Nick Desaulniers
2021-01-15 21:06 ` [PATCH v5 1/3] Remove $(cc-option,-gdwarf-4) dependency from CONFIG_DEBUG_INFO_DWARF4 Nick Desaulniers
2021-01-15 21:47 ` Sedat Dilek
2021-01-15 21:51 ` Nick Desaulniers
2021-01-15 23:54 ` Masahiro Yamada
2021-01-20 5:57 ` Masahiro Yamada
2021-01-15 21:59 ` Fangrui Song
2021-01-15 22:03 ` Sedat Dilek
2021-01-15 21:06 ` [PATCH v5 2/3] Kbuild: make DWARF version a choice Nick Desaulniers
2021-01-15 21:42 ` Sedat Dilek
2021-01-15 22:05 ` Fangrui Song
2021-01-20 20:40 ` Nathan Chancellor
2021-01-21 2:35 ` Sedat Dilek
2021-01-15 21:06 ` [PATCH v5 3/3] Kbuild: implement support for DWARF v5 Nick Desaulniers
2021-01-15 21:45 ` Sedat Dilek
2021-01-15 21:49 ` Nick Desaulniers
2021-01-15 21:57 ` Sedat Dilek
2021-01-15 21:53 ` [PATCH v5 0/3] Kbuild: DWARF v5 support Sedat Dilek
2021-01-15 23:24 ` Yonghong Song
2021-01-15 23:34 ` Nick Desaulniers
2021-01-15 23:42 ` Andrii Nakryiko
2021-01-15 23:43 ` Yonghong Song [this message]
2021-01-17 20:15 ` Arnaldo Carvalho de Melo
2021-02-04 1:31 ` Nick Desaulniers
2021-02-04 2:57 ` Andrii Nakryiko
2021-02-04 3:13 ` Nick Desaulniers
2021-02-04 23:54 ` Andrii Nakryiko
2021-02-05 0:04 ` Nick Desaulniers
2021-02-04 8:42 ` Sedat Dilek
2021-02-04 8:59 ` 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=12b6c2ca-4cf7-4edd-faf2-72e3cb59c00e@fb.com \
--to=yhs@fb.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=cmtice@google.com \
--cc=jakub@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=nickc@redhat.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;
as well as URLs for NNTP newsgroup(s).