public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
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 15:27:17 +0000	[thread overview]
Message-ID: <bug-26987-11298-IPzc9YQZYI@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 #19 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Jakub Jelinek from comment #18)
> (In reply to Mark Wielaard from comment #16)
> > > On the consumer side the question is if consumers will be able to cope with such large leb128 values.
> > 
> > In general no. At least elfutils and binutils only deal with max 64bit
> > leb128 values. Both also treat the new DWARF5 DW_FORM_data16 as a block
> > class (and not a constant class as a strict reading of the spec would imply).
> 
> Strict reading of the spec says that constant class is
> DW_FORM_data{1,2,4,8,16},
> DW_FORM_{s,u}data and DW_FORM_implicit_const, at least in DWARF5.

Right, but given that most/all consumers represent constants with max 64bit
signed/unsigned types, they cannot easily deal with DW_FORM_data16 or
excessively large leb128 values.

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

  parent reply	other threads:[~2020-12-02 15:27 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
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 [this message]
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-IPzc9YQZYI@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).