From: Yonghong Song <yhs@fb.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
<dwarves@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Bill Wendling <morbo@google.com>, bpf <bpf@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH dwarves 3/3] dwarf_loader: add option to merge more dwarf cu's into one pahole cu
Date: Fri, 26 Mar 2021 16:17:40 -0700 [thread overview]
Message-ID: <2db67186-b99c-b89a-bc56-620133d4a35c@fb.com> (raw)
In-Reply-To: <CAADnVQ+MT_u7q7veB_ws8PZ0XC0v2f2=P-TnzOBbaahbvYRDwQ@mail.gmail.com>
On 3/26/21 4:12 PM, Alexei Starovoitov wrote:
> On Fri, Mar 26, 2021 at 4:05 PM Yonghong Song <yhs@fb.com> wrote:
>>
>> Now since you found gcc actually has flags in dwarf tag producer which
>> will provides whether lto is used, I went on clang side found that
>> the following flag is needed in clang in order to embed flags in
>> the producer tag:
>> -grecord-gcc-switches
> ...
>> In Linux:
>> - add flag -grecord-gcc-switches if clang lto is enabled.
>
> I think that will help to make dwarf output a bit more uniform between
> gcc and clang. So it's a good thing on its own.
> Recording compilation flags in the debug info could be useful in
> other cases too. I would pass it for both lto and non-lto builds.
Good point. Will do this.
next prev parent reply other threads:[~2021-03-26 23:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 6:53 [PATCH dwarves 0/3] add option to merge more dwarf cu's into Yonghong Song
2021-03-25 6:53 ` [PATCH dwarves 1/3] dwarf_loader: permits flexible HASHTAGS__BITS Yonghong Song
2021-03-26 23:13 ` Andrii Nakryiko
2021-03-26 23:26 ` Yonghong Song
2021-03-29 14:02 ` Arnaldo Carvalho de Melo
2021-03-31 4:30 ` Andrii Nakryiko
2021-03-25 6:53 ` [PATCH dwarves 2/3] dwarf_loader: factor out common code to initialize a cu Yonghong Song
2021-03-25 6:53 ` [PATCH dwarves 3/3] dwarf_loader: add option to merge more dwarf cu's into one pahole cu Yonghong Song
2021-03-26 14:41 ` Arnaldo Carvalho de Melo
2021-03-26 15:18 ` Yonghong Song
2021-03-26 17:35 ` Arnaldo Carvalho de Melo
2021-03-26 18:19 ` Arnaldo Carvalho de Melo
2021-03-26 23:05 ` Yonghong Song
2021-03-26 23:12 ` Alexei Starovoitov
2021-03-26 23:17 ` Yonghong Song [this message]
2021-03-29 14:04 ` Arnaldo Carvalho de Melo
2021-03-26 15:18 ` Arnaldo Carvalho de Melo
2021-03-26 23:21 ` Andrii Nakryiko
2021-03-27 0:19 ` Yonghong Song
2021-03-25 13:10 ` [PATCH dwarves 0/3] add option to merge more dwarf cu's into Arnaldo Carvalho de Melo
2021-03-26 1:41 ` Yonghong Song
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=2db67186-b99c-b89a-bc56-620133d4a35c@fb.com \
--to=yhs@fb.com \
--cc=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=morbo@google.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