public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>,
	Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [pushed] [gdb/testsuite] Require syscall time in gdb.reverse/time-reverse.exp
Date: Fri, 24 Feb 2023 13:53:45 +0100	[thread overview]
Message-ID: <bb534cd0-a12b-8e7d-8a7b-d2f35d78cd37@suse.de> (raw)
In-Reply-To: <87bklmn6qe.fsf@tromey.com>

[-- Attachment #1: Type: text/plain, Size: 372 bytes --]

On 2/21/23 20:44, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Tom> +require {expr [have_syscall time]}
> 
> I think simply "require {have_syscall time}" should work.

Thanks for the review.

Pedro already cleaned this one up, but I found it in another test-case 
as well.

Fixed by commit below.

Thanks,
- Tom

[-- Attachment #2: 0001-gdb-testsuite-Cleanup-unnecessary-expr-from-require-.patch --]
[-- Type: text/x-patch, Size: 1009 bytes --]

From 4f688a5dd7d5710e29f0606bf1c7aede8a6d115e Mon Sep 17 00:00:00 2001
From: Tom de Vries <tdevries@suse.de>
Date: Wed, 22 Feb 2023 09:35:07 +0100
Subject: [PATCH] [gdb/testsuite] Cleanup unnecessary expr from require line

In a recent commit I've added:
...
require {expr [have_compile_flag -fsplit-stack]}
...
but actually the expr bit is unnecessary, and we can just use:
...
require {have_compile_flag -fsplit-stack}
...

Reported-By: Tom Tromey <tom@tromey.com>
---
 gdb/testsuite/gdb.base/morestack.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.base/morestack.exp b/gdb/testsuite/gdb.base/morestack.exp
index b4d22187390..cc81522a51e 100644
--- a/gdb/testsuite/gdb.base/morestack.exp
+++ b/gdb/testsuite/gdb.base/morestack.exp
@@ -15,7 +15,7 @@
 
 require is_c_compiler_gcc
 
-require {expr [have_compile_flag -fsplit-stack]}
+require {have_compile_flag -fsplit-stack}
 
 standard_testfile
 

base-commit: 0676ec3c22f096bdf98b145b720feeef9493b5bb
-- 
2.35.3


  reply	other threads:[~2023-02-24 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 13:10 Tom de Vries
2023-02-21 19:44 ` Tom Tromey
2023-02-24 12:53   ` Tom de Vries [this message]
2023-02-22 16:12 ` [PATCH] gdb.reverse/time-reverse.exp: test both time syscall and C time function (was: Re: [pushed] [gdb/testsuite] Require syscall time in gdb.reverse/time-reverse.exp) Pedro Alves
2023-02-22 17:06   ` Tom de Vries
2023-02-22 18:11     ` Pedro Alves

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=bb534cd0-a12b-8e7d-8a7b-d2f35d78cd37@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).