From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27449] dwz: 1: Unknown DWARF DW_OP_0
Date: Fri, 26 Feb 2021 20:12:18 +0000 [thread overview]
Message-ID: <bug-27449-11298-oZmIFImwNL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27449-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27449
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
Trying to track down why/how this could happen, the following might be useful:
The abstract_origin is this variable:
[3d8fe0] variable abbrev: 178
name (string) "f16"
decl_file (data1) qfloat16.h (11)
decl_line (data1) 171
decl_column (data1) 12
type (ref4) [3d8fb3]
With the following type:
[3d8fb3] base_type abbrev: 80
byte_size (data1) 2
encoding (data1) float (4)
name (strp) "__fp16"
This might explain why it only happens on arm, which is afaik the only arch
that has __fp16 as builtin type.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-26 20:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 11:43 [Bug default/27449] New: " doko at debian dot org
2021-02-21 11:43 ` [Bug default/27449] " doko at debian dot org
2021-02-21 11:44 ` doko at debian dot org
2021-02-21 17:14 ` mark at klomp dot org
2021-02-26 20:12 ` mark at klomp dot org [this message]
2021-03-02 15:45 ` vries at gcc dot gnu.org
2021-03-02 15:46 ` vries at gcc dot gnu.org
2021-03-03 15:22 ` mark at klomp dot org
2021-03-04 8:12 ` doko at debian dot org
2021-03-04 9:36 ` mliska at suse dot cz
2021-03-04 10:05 ` mliska at suse dot cz
2021-03-04 10:11 ` mliska at suse dot cz
2021-03-04 14:43 ` mark at klomp dot org
2021-03-04 15:05 ` 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-27449-11298-oZmIFImwNL@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).