public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27400] odr tests fail with -gdwarf-5
Date: Sat, 13 Feb 2021 08:37:22 +0000	[thread overview]
Message-ID: <bug-27400-11298-egXWwgN2S1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27400-11298@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27400

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
I've looked at the odr-struct.sh fail.

First of all, odr is not enabled because the language is DW_LANG_C_plus_plus_14
instead of DW_LANG_C_plus_plus, so we need this in a few places:
...
     case DW_LANG_C_plus_plus:
+    case DW_LANG_C_plus_plus_03:
+    case DW_LANG_C_plus_plus_11:
+    case DW_LANG_C_plus_plus_14:
...

Then, it seems the checksums for both struct aaa are different, because of
processing a DW_AT_decl_line with DW_FORM_implicit_const.  The const has the
same value (according to readelf), but somehow the resulting hashes are
different.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-02-13  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12  9:57 [Bug default/27400] New: " mark at klomp dot org
2021-02-12 19:19 ` [Bug default/27400] " vries at gcc dot gnu.org
2021-02-13  8:37 ` vries at gcc dot gnu.org [this message]
2021-02-13 23:18 ` vries at gcc dot gnu.org
2021-02-14  8:07 ` vries at gcc dot gnu.org
2021-02-14  8:52 ` vries at gcc dot gnu.org
2021-02-14 21:25 ` vries at gcc dot gnu.org

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=bug-27400-11298-egXWwgN2S1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).