From: "E, Nagajyothi" <Nagajyothi.E@amd.com>
To: Mark Wielaard <mark@klomp.org>,
"dwz@sourceware.org" <dwz@sourceware.org>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
"Achra, Nitika" <Nitika.Achra@amd.com>,
"Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>,
"E, Nagajyothi" <Nagajyothi.E@amd.com>
Subject: RE: Plan to contribute for supporting split dwarf (-gsplit-dwarf) in dwz
Date: Wed, 17 Feb 2021 05:53:56 +0000 [thread overview]
Message-ID: <BYAPR12MB2823338891AFB6ED1E243D9696869@BYAPR12MB2823.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210215185417.GC3149@wildebeest.org>
[AMD Official Use Only - Internal Distribution Only]
Hi,
I am working on adding support for the dwarf5 .debug_str_offsets, .debug_addr sections and the related forms DW_FORM_strx[1234], DW_FORM_addrx[1234].
Please let me know if anyone has already started work on these.
Thanks,
Nagajyothi
-----Original Message-----
From: Mark Wielaard <mark@klomp.org>
Sent: Tuesday, February 16, 2021 12:24 AM
To: Sharma, Alok Kumar <AlokKumar.Sharma@amd.com>
Cc: 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
[CAUTION: External Email]
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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceware.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D27376&data=04%7C01%7CNagajyothi.E%40amd.com%7Cedeb271285e94b3a6d6b08d8d1e3447a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637490121349829241%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HiyzxPs6SJnUE%2BMEKAsUE8HL2dvneJD1V7Yfcb9ZDcQ%3D&reserved=0
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceware.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D27375&data=04%7C01%7CNagajyothi.E%40amd.com%7Cedeb271285e94b3a6d6b08d8d1e3447a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637490121349829241%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QpjPErW8i8JG75ke528vxPry5pvkwfIq6QO3yxdxURo%3D&reserved=0
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceware.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D27373&data=04%7C01%7CNagajyothi.E%40amd.com%7Cedeb271285e94b3a6d6b08d8d1e3447a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637490121349829241%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=h4WU7ejc7KeSBEluEAgnM5%2FRMRTOVMjRXuzZVbdBlec%3D&reserved=0
See also this comment:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceware.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D24726%23c5&data=04%7C01%7CNagajyothi.E%40amd.com%7Cedeb271285e94b3a6d6b08d8d1e3447a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637490121349829241%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uLu90OuqGGBKIFwqItGHPNomPHb2HJNG8TkXKJ%2FUggM%3D&reserved=0
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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceware.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D24756&data=04%7C01%7CNagajyothi.E%40amd.com%7Cedeb271285e94b3a6d6b08d8d1e3447a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637490121349829241%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BoaV%2Fqfl7feS7siRNIsze0aZui7S9qN17vBj%2FYOkjdA%3D&reserved=0 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-17 5:53 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
2021-02-17 5:53 ` E, Nagajyothi [this message]
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=BYAPR12MB2823338891AFB6ED1E243D9696869@BYAPR12MB2823.namprd12.prod.outlook.com \
--to=nagajyothi.e@amd.com \
--cc=AlokKumar.Sharma@amd.com \
--cc=JiniSusan.George@amd.com \
--cc=Nitika.Achra@amd.com \
--cc=dwz@sourceware.org \
--cc=mark@klomp.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).