From: "Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>
To: "dwz@sourceware.org" <dwz@sourceware.org>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
"Achra, Nitika" <Nitika.Achra@amd.com>,
"E, Nagajyothi" <Nagajyothi.E@amd.com>,
"Joseph, Ancel" <Ancel.Joseph@amd.com>
Subject: RE: [PATCH] Split DWARF support for DWZ
Date: Sun, 3 Oct 2021 12:37:26 +0000 [thread overview]
Message-ID: <CO6PR12MB5491109A8BCEDEBFED95A1A59EAD9@CO6PR12MB5491.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CO6PR12MB5491CA84BD1DAE3F60259DF69EC49@CO6PR12MB5491.namprd12.prod.outlook.com>
PING !
Regards,
Alok
-----Original Message-----
From: Sharma, Alok Kumar
Sent: Monday, August 23, 2021 11:06 AM
To: dwz@sourceware.org
Cc: George, Jini Susan <JiniSusan.George@amd.com>; Achra, Nitika <Nitika.Achra@amd.com>; E, Nagajyothi <Nagajyothi.E@amd.com>; Joseph, Ancel <Ancel.Joseph@amd.com>
Subject: [PATCH] Split DWARF support for DWZ
Hi all,
I request you to please review the source modification done to support split DWARF.
Existing DWZ when deals with executable having split DWARF information
in separate file (DW_AT_GNU_dwo_name/DW_AT_dwo_name), it ignores the
separate file and only attempts to optimize main executable which has
very less information as almost all the debug information is present
in sepaterate file.
Now DWZ is modified to extract the separate file name from
atributes DW_AT_GNU_dwo_name/DW_AT_dwo_name in main executable and
calls function DWZ on separate file as well.
While processing DWO file, information is read from corresponding ".dwo"
sections in place of original one. This is assisted by macros
DEFINE_DEBUG (defining section enum) and DEFINE_SECTION (defining section
names along with other fields) in a way that very next section to the
original one is the ".dwo" variant of it. When we process DWO file we
access section using macro "INDEX(DEBUG_SECTION)", which is defined as
"(DEBUG_SECTION + is_dwo_file)". This way we avoid any duplicacy and
use existing code.
Regards,
Alok
prev parent reply other threads:[~2021-10-03 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 5:35 Sharma, Alok Kumar
2021-10-03 12:37 ` Sharma, Alok Kumar [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=CO6PR12MB5491109A8BCEDEBFED95A1A59EAD9@CO6PR12MB5491.namprd12.prod.outlook.com \
--to=alokkumar.sharma@amd.com \
--cc=Ancel.Joseph@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).