public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [pushed 1/4] [gdb/testsuite] Don't use string cat in gdb.dwarf2/dw2-abs-hi-pc.exp
Date: Tue, 2 May 2023 17:38:57 +0200	[thread overview]
Message-ID: <6d526208-a85c-fcdd-700d-3b3d8a5588d6@suse.de> (raw)
In-Reply-To: <877ctzjf37.fsf@linux-m68k.org>

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

On 4/26/23 09:08, Andreas Schwab wrote:
> On Apr 26 2023, Tom de Vries via Gdb-patches wrote:
> 
>> FWIW, reading a bit more about it I get the impression also set is
>> idiomatic, so I came up with this:
>> ...
>> set res [lmap v $l { set v $v/c ; set v }]
>> ...
>> which works as well.
> 
> You won't need the second set, though, since the first set already
> returns the assigned value.
> 

Andreas, thanks for the review.

Committed as attached.

Thanks,
- Tom


[-- Attachment #2: 0001-gdb-testsuite-Use-set-in-lmap-in-gdb.dwarf2-dw2-abs-.patch --]
[-- Type: text/x-patch, Size: 1270 bytes --]

From 2cef3ed1040d4f5191fbc53ebc82fdb3a635f7d1 Mon Sep 17 00:00:00 2001
From: Tom de Vries <tdevries@suse.de>
Date: Tue, 2 May 2023 17:28:50 +0200
Subject: [pushed] [gdb/testsuite] Use set in lmap in
 gdb.dwarf2/dw2-abs-hi-pc.exp

In gdb.dwarf2/dw2-abs-hi-pc.exp we do:
...
set sources [lmap i $sources { expr { "$srcdir/$subdir/$i" } }]
...

The use of expr is not idiomatic.  Fix this by using set instead:
...
set sources [lmap i $sources { set tmp $srcdir/$subdir/$i }]
...

Reported-By: Tom Tromey <tom@tromey.com>
Reviewed-By: Andreas Schwab <schwab@suse.de>
---
 gdb/testsuite/gdb.dwarf2/dw2-abs-hi-pc.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.dwarf2/dw2-abs-hi-pc.exp b/gdb/testsuite/gdb.dwarf2/dw2-abs-hi-pc.exp
index 2ea6a5cea00..5b5d678ec7a 100644
--- a/gdb/testsuite/gdb.dwarf2/dw2-abs-hi-pc.exp
+++ b/gdb/testsuite/gdb.dwarf2/dw2-abs-hi-pc.exp
@@ -24,7 +24,7 @@ set sources \
 	 ${testfile}.c \
 	 ${testfile}-hello.c \
 	 ${testfile}-world.c]
-set sources [lmap i $sources { expr { "$srcdir/$subdir/$i" } }]
+set sources [lmap i $sources { set tmp $srcdir/$subdir/$i }]
 
 lassign [function_range hello $sources] \
     hello_start hello_len

base-commit: b545d4239bedf9001926efd55da2aa2bd2bbb94a
-- 
2.35.3


  reply	other threads:[~2023-05-02 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 12:48 Tom de Vries
2023-04-24 12:48 ` [pushed 2/4] [gdb/testsuite] Add basic lmap for tcl < 8.6 Tom de Vries
2023-04-24 12:48 ` [pushed 3/4] [gdb/testsuite] Fix gdb.multi/multi-arch.exp on powerpc64le Tom de Vries
2023-04-24 12:48 ` [pushed 4/4] [gdb/testsuite] Require GCC >= 5.x.x in gdb.base/utf8-identifiers.exp Tom de Vries
2023-04-24 16:48 ` [pushed 1/4] [gdb/testsuite] Don't use string cat in gdb.dwarf2/dw2-abs-hi-pc.exp Tom Tromey
2023-04-24 20:22   ` Tom de Vries
2023-04-25 18:38     ` Tom Tromey
2023-04-26  6:34       ` Tom de Vries
2023-04-26  7:08         ` Andreas Schwab
2023-05-02 15:38           ` Tom de Vries [this message]
2023-04-27 13:39         ` Tom Tromey
2023-05-02 15:40           ` Tom de Vries

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=6d526208-a85c-fcdd-700d-3b3d8a5588d6@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.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).