From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [RFC] [gdb/testsuite] Use dwarf assembly in gdb.dlang/dlang-start.exp
Date: Mon, 27 Mar 2023 13:51:40 +0200 [thread overview]
Message-ID: <e3ecb991-5471-1a2b-b542-cde38264e98a@suse.de> (raw)
In-Reply-To: <20230220134839.1944-1-tdevries@suse.de>
On 2/20/23 14:48, Tom de Vries via Gdb-patches wrote:
> so let's rewrite the test-case using dwarf assembly
> (though arguably, it's not a bad idea to have test-cases excercising
> actual compilers).
I ended up solving this conundrum by moving the dwarf assembly into a
separate test-case (
https://sourceware.org/pipermail/gdb-patches/2023-March/198314.html ).
Thanks,
- Tom
prev parent reply other threads:[~2023-03-27 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 13:48 Tom de Vries
2023-02-20 14:14 ` Iain Buclaw
2023-02-20 14:28 ` Tom de Vries
2023-03-27 11:51 ` Tom de Vries [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=e3ecb991-5471-1a2b-b542-cde38264e98a@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).