From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdb/testsuite] Generate .debug_aranges entry for dummy CU
Date: Fri, 27 Aug 2021 07:42:19 -0600 [thread overview]
Message-ID: <875yvrovgk.fsf@tromey.com> (raw)
In-Reply-To: <20210826115816.GA22826@delia> (Tom de Vries via Gdb-patches's message of "Thu, 26 Aug 2021 13:58:17 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> A best practise for DWARF [1] is to generate .debug_aranges entries for CUs
Tom> even if they have no address range.
Tom> Generate .debug_arange entries for the dummy CUs added by the DWARF assembler.
Tom> Tested on x86_64-linux.
Tom> [1] http://wiki.dwarfstd.org/index.php?title=Best_Practices
Tom> Any comments?
Tom> + declare_labels dummy_cu
If there are two dummy CUs, won't the labels clash?
Tom
next prev parent reply other threads:[~2021-08-27 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 11:58 Tom de Vries via Gdb-patches
2021-08-27 13:42 ` Tom Tromey [this message]
2021-08-27 14:52 ` Tom de Vries via Gdb-patches
2021-08-27 16:40 ` Tom Tromey
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=875yvrovgk.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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