From: Nick Desaulniers <ndesaulniers@google.com>
To: yhs@fb.com
Cc: andrii@kernel.org, arnaldo.melo@gmail.com, ast@kernel.org,
bpf@vger.kernel.org, dwarves@vger.kernel.org, kernel-team@fb.com,
morbo@google.com, clang-built-linux@googlegroups.com,
sedat.dilek@gmail.com, Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH dwarves v3 0/3] permit merging all dwarf cu's for clang lto built binary
Date: Mon, 29 Mar 2021 16:14:13 -0700 [thread overview]
Message-ID: <20210329231413.1971368-1-ndesaulniers@google.com> (raw)
In-Reply-To: <20210328201400.1426437-1-yhs@fb.com>
(replying manually to https://lore.kernel.org/dwarves/20210328201400.1426437-1-yhs@fb.com/)
I didn't validate or try to use the produced data, but with this and the
kernel patch
https://lore.kernel.org/bpf/20210328064121.2062927-1-yhs@fb.com/
I was able to build a x86_64 defconfig + CONFIG_LTO_CLANG_THIN +
CONFIG_DEBUG_INFO_BTF without further errors. Thank you for the series! FWIW:
Tested-by: Nick Desaulniers <ndesaulniers@google.com>
prev parent reply other threads:[~2021-03-29 23:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 20:14 [PATCH dwarves v3 0/3] permit merging all dwarf cu's for clang lto built binary Yonghong Song
2021-03-28 20:14 ` [PATCH dwarves v3 1/3] dwarf_loader: permits flexible HASHTAGS__BITS Yonghong Song
2021-03-28 20:14 ` [PATCH dwarves v3 2/3] dwarf_loader: factor out common code to initialize a cu Yonghong Song
2021-03-28 20:14 ` [PATCH dwarves v3 3/3] dwarf_loader: permit merging all dwarf cu's for clang lto built binary Yonghong Song
2021-03-30 20:08 ` Bill Wendling
2021-03-30 20:15 ` Yonghong Song
2021-03-30 21:44 ` Bill Wendling
2021-03-30 22:28 ` Yonghong Song
2021-03-30 23:25 ` Bill Wendling
2021-03-29 17:40 ` [PATCH dwarves v3 0/3] " Arnaldo Carvalho de Melo
2021-03-30 15:10 ` Arnaldo Carvalho de Melo
2021-03-30 18:08 ` Arnaldo Carvalho de Melo
2021-03-30 18:24 ` Arnaldo Carvalho de Melo
2021-03-31 3:20 ` Yonghong Song
2021-03-31 13:54 ` Arnaldo Carvalho de Melo
2021-03-31 15:08 ` Yonghong Song
2021-03-31 0:29 ` Yonghong Song
2021-03-29 23:14 ` Nick Desaulniers [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=20210329231413.1971368-1-ndesaulniers@google.com \
--to=ndesaulniers@google.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dwarves@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=morbo@google.com \
--cc=sedat.dilek@gmail.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).