From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/26987] GCC 11 Ada binaries contain unknown tags
Date: Wed, 02 Dec 2020 13:09:45 +0000 [thread overview]
Message-ID: <bug-26987-11298-Ykddudjowx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26987-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26987
--- Comment #9 from Mark Wielaard <mark at klomp dot org> ---
This is what eu-readelf says about the same:
[ 54630] subrange_type abbrev: 32
lower_bound (block1)
[ 0] ??? (0)
[ 1] ??? (0)
[ 2] ??? (0)
[ 3] ??? (0)
[ 4] ??? (0)
[ 5] ??? (0)
[ 6] ??? (0)
[ 7] ??? (0)
[ 8] ??? (0)
[ 9] ??? (0)
[10] ??? (0)
[11] ??? (0)
[12] ??? (0)
[13] ??? (0)
[14] ??? (0)
[15] breg16 <TRUNCATED>
upper_bound (block1)
[ 0] lo_user+0x1f
[ 1] lo_user+0x1f
[ 2] lo_user+0x1f
[ 3] lo_user+0x1f
[ 4] lo_user+0x1f
[ 5] lo_user+0x1f
[ 6] lo_user+0x1f
[ 7] lo_user+0x1f
[ 8] lo_user+0x1f
[ 9] lo_user+0x1f
[10] lo_user+0x1f
[11] lo_user+0x1f
[12] lo_user+0x1f
[13] lo_user+0x1f
[14] lo_user+0x1f
[15] breg15 <TRUNCATED>
name (strp)
"system__put_images__lll_integer_images__integer_typeXn"
type (ref4) [ 54660]
So this is encoded as DW_FORM_block1, which is not a valid form for
DW_AT_upper_bound or DW_AT_lower_bound. According the the DWARF spec only
constant, exprloc, reference classes are.
Both readelfs and dwz seem to interpret this DW_FORM_block1 as an exprloc,
which is arguably wrong (since DWARF4 there is DW_FORM_exprloc).
In DWARF3 a DW_AT_upperbound could be represented by block, constant,
reference. But then section 2.19 said: "For a block, the value is interpreted
as a DWARF expression; evaluation of the expression yields the value of the
attribute."
In DWARF5 there is DW_FORM_data16, which could be used as a constant to express
really big constants.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-02 13:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 11:22 [Bug default/26987] New: " mliska at suse dot cz
2020-12-01 11:38 ` [Bug default/26987] " jakub at redhat dot com
2020-12-02 8:25 ` mliska at suse dot cz
2020-12-02 10:06 ` mark at klomp dot org
2020-12-02 10:27 ` mliska at suse dot cz
2020-12-02 10:56 ` mark at klomp dot org
2020-12-02 12:29 ` mliska at suse dot cz
2020-12-02 12:31 ` mliska at suse dot cz
2020-12-02 12:51 ` mark at klomp dot org
2020-12-02 13:09 ` mark at klomp dot org [this message]
2020-12-02 14:19 ` tromey at sourceware dot org
2020-12-02 14:26 ` jakub at redhat dot com
2020-12-02 14:35 ` mark at klomp dot org
2020-12-02 14:40 ` jakub at redhat dot com
2020-12-02 15:08 ` jakub at redhat dot com
2020-12-02 15:14 ` mark at klomp dot org
2020-12-02 15:17 ` mark at klomp dot org
2020-12-02 15:18 ` jakub at redhat dot com
2020-12-02 15:21 ` jakub at redhat dot com
2020-12-02 15:27 ` mark at klomp dot org
2020-12-02 15:35 ` tromey at sourceware dot org
2020-12-02 16:05 ` ebotcazou at gcc dot gnu.org
2020-12-02 23:46 ` jakub at redhat dot com
2021-02-13 22:52 ` mark at klomp dot org
2021-02-18 21:19 ` mark at klomp dot 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-26987-11298-Ykddudjowx@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).