From: Mark Wielaard <mark@klomp.org>
To: "George, Jini Susan" <JiniSusan.George@amd.com>,
"dwz@sourceware.org" <dwz@sourceware.org>
Subject: Re: Release plans for the next version of dwz ?
Date: Mon, 18 Jan 2021 10:27:51 +0100 [thread overview]
Message-ID: <c2fbc64b9e25804b67b46cda6d3033f891a342d1.camel@klomp.org> (raw)
In-Reply-To: <BY5PR12MB4965CBA46A3F40A73196926690D10@BY5PR12MB4965.namprd12.prod.outlook.com>
Hi Jini,
On Tue, 2021-01-05 at 06:32 +0000, George, Jini Susan via Dwz wrote:
> I noticed that over the past year, a lot of modifications went into
> dwz to support DWARFv5. I would like to know if there are any
> upcoming plans to release a version of dwz.
I believe the DWARFv5 support is complete now with my last 2 commits
when not combined with --odr.
There are still failures with the ODR support when building the
testcases with -gdwarf-5, specifically:
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-class-ns.sh
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-def-decl.sh
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-loc.sh
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-struct.sh
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-struct-ns.sh
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-union.sh
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-class.sh
FAIL: /opt/local/src/dwz/testsuite/dwz.tests/odr-union-ns.sh
It looks like ODR detection simply doesn't work with DWARF5, so no size
reduction is produced. I haven't figured out why yet.
That said, it would be nice to see a new release. We can always say
that ODR support is experimental and doesn't yet work for DWARF5.
Cheers,
Mark
next prev parent reply other threads:[~2021-01-18 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 6:32 George, Jini Susan
2021-01-18 9:27 ` Mark Wielaard [this message]
2021-01-19 16:34 ` George, Jini Susan
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=c2fbc64b9e25804b67b46cda6d3033f891a342d1.camel@klomp.org \
--to=mark@klomp.org \
--cc=JiniSusan.George@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).