From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27368] [dwz, dwarf5] Handle .debug_macro version 5
Date: Mon, 08 Feb 2021 14:39:45 +0000 [thread overview]
Message-ID: <bug-27368-11298-2YJuwylsYQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27368-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27368
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #7 from Mark Wielaard <mark at klomp dot org> ---
The version check should be fine.
My preference would simply be version != 4 && version !=5.
This should fine as is with GCC DWARF5 since:
DW_MACRO_GNU_define == DW_MACRO_define
DW_MACRO_GNU_undef == DW_MACRO_undef
DW_MACRO_GNU_start_file == DW_MACRO_start_file
DW_MACRO_GNU_end_file == DW_MACRO_end_file
DW_MACRO_GNU_define_indirect == DW_MACRO_define_strp
DW_MACRO_GNU_undef_indirect == DW_MACRO_undef_strp
DW_MACRO_GNU_transparent_include == DW_MACRO_import
That leaves:
DW_MACRO_define_strx
DW_MACRO_undef_strx
But those are never generated by GCC (see also DW_FORM_strx[1234] support).
dwz itself could generate (probably behind a --dwarf5 flag):
DW_MACRO_define_sup
DW_MACRO_undef_sup
DW_MACRO_import_sup
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-08 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 10:51 [Bug default/27368] New: " vries at gcc dot gnu.org
2021-02-08 10:54 ` [Bug default/27368] " vries at gcc dot gnu.org
2021-02-08 10:55 ` vries at gcc dot gnu.org
2021-02-08 10:57 ` jakub at redhat dot com
2021-02-08 11:28 ` vries at gcc dot gnu.org
2021-02-08 11:36 ` jakub at redhat dot com
2021-02-08 11:43 ` vries at gcc dot gnu.org
2021-02-08 14:39 ` mark at klomp dot org [this message]
2021-02-09 7:36 ` vries at gcc dot gnu.org
2021-02-09 7:42 ` 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-27368-11298-2YJuwylsYQ@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).