From: Mark Wielaard <mark@klomp.org>
To: "Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>
Cc: "dwz@sourceware.org" <dwz@sourceware.org>,
"George, Jini Susan" <JiniSusan.George@amd.com>,
"E, Nagajyothi" <Nagajyothi.E@amd.com>,
"Achra, Nitika" <Nitika.Achra@amd.com>
Subject: Re: Plan to contribute for supporting split dwarf (-gsplit-dwarf) in dwz
Date: Mon, 15 Feb 2021 19:54:17 +0100 [thread overview]
Message-ID: <20210215185417.GC3149@wildebeest.org> (raw)
In-Reply-To: <BYAPR12MB322363A02A435BFB73398B0A9E889@BYAPR12MB3223.namprd12.prod.outlook.com>
Hi Alok,
On Mon, Feb 15, 2021 at 05:26:29PM +0000, Sharma, Alok Kumar via Dwz wrote:
> I am planning to contribute for supporting split DWARF.
>
> Please let me know if it is already being worked on?
That is great. Nobody is currently working on that as far as I
know. One issue to resolve is knowing how to "unsplit" the DWARF
first. Since it isn't clear (to me) whether it makes sense to do split
DWARF .dwo (sections/files) together with Supplementary DWARF Object
references. One idea might be to handle DWP processed files?
There are a couple of bugs that might be prerequirements for handling
split DWARF, you probably need "split" variants of these bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=27376
https://sourceware.org/bugzilla/show_bug.cgi?id=27375
https://sourceware.org/bugzilla/show_bug.cgi?id=27373
See also this comment:
https://sourceware.org/bugzilla/show_bug.cgi?id=24726#c5
Which describes some other issues, like DW_FORM_strx, .debug_str_offset,
DW_FORM_rnglistx and various _base attributes that need supporting.
(This should probabably have their own bugs filed.)
There is already one explicit -gsplit-dwarf variant bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=24756 But that is only
for part of the problem (and might be simply resolved by bug #27375).
Cheers,
Mark
next prev parent reply other threads:[~2021-02-15 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 17:26 Sharma, Alok Kumar
2021-02-15 18:54 ` Mark Wielaard [this message]
2021-02-17 5:53 ` E, Nagajyothi
2021-02-18 14:45 ` Mark Wielaard
2021-02-22 3:39 ` E, Nagajyothi
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=20210215185417.GC3149@wildebeest.org \
--to=mark@klomp.org \
--cc=AlokKumar.Sharma@amd.com \
--cc=JiniSusan.George@amd.com \
--cc=Nagajyothi.E@amd.com \
--cc=Nitika.Achra@amd.com \
--cc=dwz@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).