From: Alan Modra <amodra@gmail.com>
To: YunQiang Su <yunqiang.su@cipunited.com>
Cc: binutils@sourceware.org, nickc@redhat.com
Subject: Re: [PATCH] ld: Use run_host_cmd_yesno in indirect.exp instead of catch exec
Date: Thu, 6 Jul 2023 07:00:13 +0930 [thread overview]
Message-ID: <ZKXg5ThdKhlST2pm@squeak.grove.modra.org> (raw)
In-Reply-To: <20230630060757.2006878-1-yunqiang.su@cipunited.com>
On Fri, Jun 30, 2023 at 02:07:57PM +0800, YunQiang Su wrote:
> Catch "exec $CC_FOR_TARGET" won't use the gas/ld that we just build,
> and in fact run_host_cmd_yesno is a better choice for it.
>
> ld/ChangeLog:
>
> * testsuite/ld-elf/indirect.exp: use run_host_cmd_yesno
> instead of handwrite catch exec $CC_FOR_TARGET.
OK, yes, we should be using run_host_cmd everywhere we invoke a
compiler in the ld testsuite. One reason being that run_host_cmd
properly inserts $gcc_B_opt in cases where a user wants to test
binutils with a newly built compiler, ie. when $CC specifies -B.
I'm going to apply this one too.
* testsuite/ld-elf/no-section-header.exp (binutils_run_test):
Use run_host_cmd to invoke $CC.
diff --git a/ld/testsuite/ld-elf/no-section-header.exp b/ld/testsuite/ld-elf/no-section-header.exp
index c010e572a32..2d8c687dc0a 100644
--- a/ld/testsuite/ld-elf/no-section-header.exp
+++ b/ld/testsuite/ld-elf/no-section-header.exp
@@ -136,7 +136,6 @@ if { ![isnative] || ![check_shared_lib_support] } {
proc binutils_run_test { prog } {
global CC
- global gcc_B_opt
global READELF
global NM
global objcopy
@@ -354,8 +353,7 @@ proc binutils_run_test { prog } {
return
}
- send_log "$CC $gcc_B_opt -o tmpdir/pr25617-1 tmpdir/pr25617-1b.o tmpdir/pr25617-1a-now-no-sec-hdr.so\n"
- catch "exec $CC $gcc_B_opt -o tmpdir/pr25617-1 tmpdir/pr25617-1b.o tmpdir/pr25617-1a-now-no-sec-hdr.so" got
+ set got [run_host_cmd $CC "-o tmpdir/pr25617-1 tmpdir/pr25617-1b.o tmpdir/pr25617-1a-now-no-sec-hdr.so"]
if ![string match "*pr25617-1a-now-no-sec-hdr.so*file in wrong format*" $got] then {
send_log "$got\n"
fail "Update pr25617-1a-now-no-sec-hdr.so ($prog_name)"
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2023-07-05 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 6:07 YunQiang Su
2023-07-05 21:30 ` Alan Modra [this message]
2023-07-07 8:48 ` Nick Clifton
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=ZKXg5ThdKhlST2pm@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=yunqiang.su@cipunited.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).