From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] [gdb/testsuite] Fix some dwarf assembly test-cases
Date: Thu, 21 May 2026 08:07:26 -0600 [thread overview]
Message-ID: <87v7cgamap.fsf@tromey.com> (raw)
In-Reply-To: <20260520153832.3600888-1-tdevries@suse.de> (Tom de Vries's message of "Wed, 20 May 2026 17:38:29 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> I ran readelf -w on the executable from test-case
Tom> gdb.dwarf2/imported-unit-c.exp, and saw some warnings.
Tom> This patch series fixes those, and a few more warnings in other test-cases
Tom> that I found using readelf -w and llvm-dwarfdump -a.
Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34157
These all look good to me, thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2026-05-21 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 15:38 Tom de Vries
2026-05-20 15:38 ` [PATCH 1/3] [gdb/testsuite] Clean up gdb.dwarf2/imported-unit-c.exp Tom de Vries
2026-05-20 15:38 ` [PATCH 2/3] [gdb/testsuite] Clean up duplicate .debug_aranges terminators Tom de Vries
2026-05-20 15:38 ` [PATCH 3/3] [gdb/testsuite] Don't generate dummy CUs in dwz files Tom de Vries
2026-05-21 14:07 ` Tom Tromey [this message]
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=87v7cgamap.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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