From: Jakub Jelinek <jakub@redhat.com>
To: Arvind Sankar <nivedita@alum.mit.edu>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sedat Dilek <sedat.dilek@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Fangrui Song <maskray@google.com>,
Caroline Tice <cmtice@google.com>,
Nick Clifton <nickc@redhat.com>, Yonghong Song <yhs@fb.com>,
Jiri Olsa <jolsa@kernel.org>, Andrii Nakryiko <andrii@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH v6 1/2] Kbuild: make DWARF version a choice
Date: Fri, 29 Jan 2021 22:41:37 +0100 [thread overview]
Message-ID: <20210129214137.GW4020736@tucnak> (raw)
In-Reply-To: <YBR+8KLWnjnMfP6i@rani.riverdale.lan>
On Fri, Jan 29, 2021 at 04:32:32PM -0500, Arvind Sankar wrote:
> Given what Jakub is saying, i.e. it was previously impossible to get
> dwarf2 with gcc, and you get dwarf4 whether or not DEBUG_INFO_DWARF4 was
It isn't impossible to get it, -gdwarf-2 works, it is just not a very good
choice (at least unless one knows some debug info consumer is not DWARF3 or
later ready).
Though, even gcc -gdwarf-2 will use many extensions from DWARF3 and later,
as long as there is no way to describe stuff in DWARF2. -gstrict-dwarf
option requests that no DWARF extensions are used.
Jakub
next prev parent reply other threads:[~2021-01-29 21:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:43 [PATCH v6 0/2] Kbuild: DWARF v5 support Nick Desaulniers
2021-01-29 19:43 ` [PATCH v6 1/2] Kbuild: make DWARF version a choice Nick Desaulniers
2021-01-29 20:17 ` Jakub Jelinek
2021-01-29 20:19 ` Nick Desaulniers
2021-01-29 20:57 ` Nick Desaulniers
2021-01-29 21:32 ` Arvind Sankar
2021-01-29 21:41 ` Jakub Jelinek [this message]
2021-01-29 22:40 ` Nick Desaulniers
2021-01-29 19:43 ` [PATCH v6 2/2] Kbuild: implement support for DWARF v5 Nick Desaulniers
2021-01-29 20:41 ` Sedat Dilek
2021-01-29 20:48 ` Nick Desaulniers
2021-01-29 20:54 ` Sedat Dilek
2021-01-29 21:09 ` Nick Desaulniers
2021-01-29 21:13 ` Sedat Dilek
2021-01-29 21:20 ` Sedat Dilek
2021-01-29 22:09 ` Nick Desaulniers
2021-01-29 22:11 ` Sedat Dilek
2021-01-29 22:20 ` Nick Desaulniers
2021-01-29 22:23 ` Sedat Dilek
2021-01-29 22:31 ` Nick Desaulniers
2021-01-29 22:42 ` Sedat Dilek
2021-02-03 7:56 ` Masahiro Yamada
2021-01-29 20:57 ` Jakub Jelinek
2021-01-29 21:05 ` Nick Desaulniers
2021-01-29 21:11 ` Jakub Jelinek
2021-01-29 22:05 ` Nick Desaulniers
2021-01-29 22:09 ` Jakub Jelinek
2021-01-29 23:25 ` Nick Desaulniers
2021-01-29 23:30 ` Nick Desaulniers
2021-01-29 22:27 ` Nick Desaulniers
2021-01-29 21:51 ` Fangrui Song
2021-01-29 22:07 ` Nick Desaulniers
2021-01-29 22:47 ` Fangrui Song
2021-01-29 20:03 ` [PATCH v6 0/2] Kbuild: DWARF v5 support Sedat Dilek
2021-01-30 0:08 ` Sedat Dilek
2021-01-30 0:46 ` Nick Desaulniers
2021-01-30 0:58 ` Fāng-ruì Sòng
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=20210129214137.GW4020736@tucnak \
--to=jakub@redhat.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=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=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nickc@redhat.com \
--cc=nivedita@alum.mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.