From: Pedro Alves <pedro@palves.net>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
gdb-patches@sourceware.org
Cc: Christophe Lyon <christophe.lyon@linaro.org>
Subject: Re: [PATCH v2 3/5] gdb/testsuite: Add gdb.arch/aarch64-mops-watchpoint.exp
Date: Fri, 10 May 2024 14:32:47 +0100 [thread overview]
Message-ID: <42b9869a-2012-4657-bae4-e8e2bb3a89a4@palves.net> (raw)
In-Reply-To: <20240507022249.554831-4-thiago.bauermann@linaro.org>
On 2024-05-07 03:22, Thiago Jung Bauermann wrote:
> +# Run a test on the target to see if it supports Aarch64 MOPS (Memory
> +# Operations) extensions. Return 0 if so, 1 if it does not.
This
"Return 0 if so, 1 if it does not."
comment seems backwards.
> Note this causes
> +# a restart of GDB.
Might want to apply a similar logic to can_spawn_for_attach, wrt gdb_exit.
See the tail end of that function. Maybe we can factor that out and
reuse it.
> +
> +gdb_caching_proc allow_aarch64_mops_tests {} {
next prev parent reply other threads:[~2024-05-10 13:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 2:22 [PATCH v2 0/5] Add support for AArch64 MOPS instructions Thiago Jung Bauermann
2024-05-07 2:22 ` [PATCH v2 1/5] gdb/aarch64: Implement software single stepping for " Thiago Jung Bauermann
2024-05-10 13:23 ` Pedro Alves
2024-05-21 21:40 ` Thiago Jung Bauermann
2024-05-22 10:51 ` Luis Machado
2024-05-07 2:22 ` [PATCH v2 2/5] gdb/aarch64: Add record support " Thiago Jung Bauermann
2024-05-07 2:22 ` [PATCH v2 3/5] gdb/testsuite: Add gdb.arch/aarch64-mops-watchpoint.exp Thiago Jung Bauermann
2024-05-10 13:32 ` Pedro Alves [this message]
2024-05-21 21:03 ` Thiago Jung Bauermann
2024-05-22 9:22 ` Tom de Vries
2024-05-22 15:38 ` Tom Tromey
2024-05-22 16:43 ` Thiago Jung Bauermann
2024-05-07 2:22 ` [PATCH v2 4/5] gdb/testsuite: Add gdb.arch/aarch64-mops-atomic-inst.exp Thiago Jung Bauermann
2024-05-07 2:22 ` [PATCH v2 5/5] gdb/testsuite: Add gdb.reverse/aarch64-mops.exp Thiago Jung Bauermann
2024-05-08 8:52 ` [PATCH v2 0/5] Add support for AArch64 MOPS instructions Luis Machado
2024-05-09 3:24 ` Thiago Jung Bauermann
2024-05-10 5:20 ` Thiago Jung Bauermann
2024-05-10 13:11 ` Luis Machado
2024-05-10 15:07 ` Guinevere Larsen
2024-05-23 1:43 ` Thiago Jung Bauermann
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=42b9869a-2012-4657-bae4-e8e2bb3a89a4@palves.net \
--to=pedro@palves.net \
--cc=christophe.lyon@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.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).