public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"cel@us.ibm.com" <cel@us.ibm.com>
Subject: Re: [PATCH ver 3] Fix hardware watchpoint check in test gdb.base/watchpoint-reuse-slot.exp
Date: Thu, 18 Aug 2022 14:31:57 +0000	[thread overview]
Message-ID: <01b41aa2582852453aadb3ab5cdc80230e60eac2.camel@de.ibm.com> (raw)
In-Reply-To: <d9af5bc09e49c29b563ef1ba1fcd48b820de6c21.camel@us.ibm.com>

Carl Love <cel@us.ibm.com> wrote:

>+# The skip_hw_watchpoint_tests checks if watchpoints are supported by
the
>+# processor.  On PowerPC, the check runs a small test program under
gdb
>+# to determine if the Power processor supports HW watchpoints.  The
check
>+# must be done before starting the test so as to not disrupt the
execution
>+# of the actual test.
>+
>+set skip_hw_watchpoint_tests_p [skip_hw_watchpoint_tests]

>-if { ![target_info exists gdb,no_hardware_watchpoints]} {
>+if { ![skip_hw_breakpoint_tests] } {

I guess this will *work* as the skip_hw_breakpoint_tests
function uses a cache to avoid re-running the test.

But it would seem more logical here to use the 
skip_hw_watchpoint_tests_p variable defined above.

Bye,
Ulrich


  reply	other threads:[~2022-08-18 14:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10  0:00 [PATCH] " Carl Love
2022-08-10 15:17 ` will schmidt
2022-08-10 17:54   ` Carl Love
2022-08-10 19:17     ` Carl Love
2022-08-11 14:16       ` will schmidt
2022-08-11 15:22         ` Carl Love
2022-08-10 19:46 ` [PATCH ver 2] " Carl Love
2022-08-12 12:23   ` Ulrich Weigand
2022-08-12 15:44     ` Carl Love
2022-08-12 16:06     ` [PATCH ver 3] " Carl Love
2022-08-18 14:31       ` Ulrich Weigand [this message]
2022-08-18 23:09         ` Carl Love
2022-09-07 22:54       ` [PATCH ver 4] " Carl Love
2022-09-08 14:11         ` Ulrich Weigand

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=01b41aa2582852453aadb3ab5cdc80230e60eac2.camel@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=cel@us.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).