public inbox for
 help / color / mirror / Atom feed
From: Tom de Vries <>
To: Mark Wielaard <>,
Subject: Re: dwz 0.14 release?
Date: Thu, 11 Feb 2021 10:15:04 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2/10/21 1:06 PM, Mark Wielaard wrote:
> Hi,
> I was wondering what we still need to do to get a 0.14 release out?
> It would be nice to release now that we support DWARF5 as GCC11 outputs
> it by default now. There are some DWARF5 constructs we still don't
> support, but they aren't really required because they are non-default.
> The only real issue is the combination of DWARF5 and dwz --odr. We see
> the following failures in the testsuite:
> There are still failures with the ODR support when building the
> testcases with -gdwarf-5, specifically:
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> FAIL: /opt/local/src/dwz/testsuite/dwz.tests/
> I haven't really investigated why that is. But we can always say
> that ODR support is experimental and doesn't yet work for DWARF5.

I can't reproduce this, can you open an PR with more details?

Anyway, odr will be experimental.  It still need to marked as such.

Furthermore, I still need to go through the PR list and clean up.

- Tom

  reply	other threads:[~2021-02-11  9:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 12:06 Mark Wielaard
2021-02-11  9:15 ` Tom de Vries [this message]
2021-02-12 10:08   ` Mark Wielaard
2021-02-19  1:16     ` Mark Wielaard
2021-02-26 23:37       ` Mark Wielaard
2021-03-01 10:49         ` tdevries
2021-03-01 11:17           ` Mark Wielaard
2021-03-01 12:40             ` Tom de Vries
2021-03-05  7:26           ` Tom de Vries
2021-03-05 16:24             ` Tom de Vries
2021-03-08  7:14               ` Tom de Vries
2021-03-08  7:22                 ` Mark Wielaard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).