public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "George, Jini Susan" <JiniSusan.George@amd.com>
To: "maxzor@maxzor.eu" <maxzor@maxzor.eu>,
	"dwz@sourceware.org" <dwz@sourceware.org>
Cc: "E, Nagajyothi" <Nagajyothi.E@amd.com>,
	"Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>
Subject: Re: dwz & DWARF 5 - .debug_addr
Date: Thu, 24 Feb 2022 13:20:08 +0000	[thread overview]
Message-ID: <BY5PR12MB4965160B7CC05A4F684D9F0D903D9@BY5PR12MB4965.namprd12.prod.outlook.com> (raw)

[AMD Official Use Only]

Hello Maxime,

We have submitted a few patches for complete DWARFv5 support (including support for .debug_addr) -- all the patches are awaiting review. Listing the links to a few of the mails here.

https://sourceware.org/pipermail/dwz/2021q2/001246.html <== the mail regarding the .debug_addr patch

https://sourceware.org/pipermail/dwz/2021q2/001247.html <== Test script modifications to use llvm-dwarfdump when compiler is clang

https://sourceware.org/pipermail/dwz/2021q3/001266.html <== Split DWARF support for DWZ

If the reviewers could help us with this, it would be great. Will repost the patches.

Thanks,
Jini.

=============================================================
This time, this mail should be targeted at the right persons ':)

On 2/12/22 21:46, Maxime Chambonnet wrote:
> CC-ing debian-ai@l.d.o, please pardon the spam
>
> On 2/12/22 21:45, Maxime Chambonnet wrote:
>> Dear GCC maintainers,
>>
>> I am dealing with a package that tries to make full use of DWARF 5 [1].
>> I try to help the ROCm Debian packaging team [2].
>> Do you have a VCS or a source repository? It is marked unknown on the
>> package page [3]. Is there work-in-progress to support .debug_addr?[4]
>>
>> Best regards, Maxime
>>
>> [1] https://github.com/ROCm-Developer-Tools/hipamd/issues/17
>> [2] https://salsa.debian.org/rocm-team
>> [3] https://tracker.debian.org/pkg/dwz
>> [4] https://manpages.debian.org/testing/dwz/dwz.1.en.html
>

             reply	other threads:[~2022-02-24 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 13:20 George, Jini Susan [this message]
     [not found] <657a3b67-385a-0210-bf55-7037e6234df5@maxzor.eu>
     [not found] ` <663a60fb-2631-a9a2-a068-e2ee9cbb12f9@maxzor.eu>
2022-02-12 21:26   ` Maxime Chambonnet

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=BY5PR12MB4965160B7CC05A4F684D9F0D903D9@BY5PR12MB4965.namprd12.prod.outlook.com \
    --to=jinisusan.george@amd.com \
    --cc=AlokKumar.Sharma@amd.com \
    --cc=Nagajyothi.E@amd.com \
    --cc=dwz@sourceware.org \
    --cc=maxzor@maxzor.eu \
    /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).