From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by sourceware.org (Postfix) with ESMTPS id B65E8384241C for ; Thu, 11 Feb 2021 09:15:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B65E8384241C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tdevries@suse.de X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id D0D2CB1E6; Thu, 11 Feb 2021 09:15:05 +0000 (UTC) Subject: Re: dwz 0.14 release? To: Mark Wielaard , dwz@sourceware.org References: <5b6633862f257bac99fa3fccfde18b931ad10cf2.camel@klomp.org> From: Tom de Vries Message-ID: <59176fae-d720-5a9c-e69c-2553706b7ff1@suse.de> Date: Thu, 11 Feb 2021 10:15:04 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: <5b6633862f257bac99fa3fccfde18b931ad10cf2.camel@klomp.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: dwz@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Dwz mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2021 09:15:10 -0000 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/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 > > 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. Thanks, - Tom