From: YunQiang Su <yunqiang.su@cipunited.com>
To: macro@orcam.me.uk
Cc: binutils@sourceware.org, YunQiang Su <yunqiang.su@cipunited.com>
Subject: [PATCH v3 1/2] GAS/MIPS: Convert module-defer-warn2 to .d format
Date: Fri, 29 Sep 2023 11:05:25 -0400 [thread overview]
Message-ID: <20230929150526.3149431-2-yunqiang.su@cipunited.com> (raw)
In-Reply-To: <20230929150526.3149431-1-yunqiang.su@cipunited.com>
The .d format can gives more control.
In fact for r2+ targets, the error message will be different.
---
gas/testsuite/gas/mips/mips.exp | 2 +-
gas/testsuite/gas/mips/module-defer-warn2.d | 4 ++++
2 files changed, 5 insertions(+), 1 deletion(-)
create mode 100644 gas/testsuite/gas/mips/module-defer-warn2.d
diff --git a/gas/testsuite/gas/mips/mips.exp b/gas/testsuite/gas/mips/mips.exp
index 91cf8b11077..13c48cd9400 100644
--- a/gas/testsuite/gas/mips/mips.exp
+++ b/gas/testsuite/gas/mips/mips.exp
@@ -2059,7 +2059,7 @@ if { [istarget mips*-*-vxworks*] } {
run_dump_test "module-override"
run_dump_test "module-defer-warn1"
- run_list_test "module-defer-warn2" "-32"
+ run_dump_test "module-defer-warn2"
foreach testopt [list -mfp32 -mfpxx -mfp64 "-mfp64-noodd" \
-msingle-float -msoft-float] {
diff --git a/gas/testsuite/gas/mips/module-defer-warn2.d b/gas/testsuite/gas/mips/module-defer-warn2.d
new file mode 100644
index 00000000000..afe086f84b0
--- /dev/null
+++ b/gas/testsuite/gas/mips/module-defer-warn2.d
@@ -0,0 +1,4 @@
+#name: .module deferred warnings 2
+#source: module-defer-warn2.s
+#as: -32
+#error_output: module-defer-warn2.l
--
2.39.2
next prev parent reply other threads:[~2023-09-29 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:05 [PATCH v3 0/2] GAS/MIPS: Fix testcase module-defer-warn2 for r2+ triples YunQiang Su
2023-09-29 15:05 ` YunQiang Su [this message]
2023-09-29 15:05 ` [PATCH v3 2/2] GAS/MIPS: Add module-defer-warn2-r2 testcase " YunQiang Su
2023-10-07 15:50 ` [PATCH v3 0/2] GAS/MIPS: Fix testcase module-defer-warn2 " YunQiang Su
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=20230929150526.3149431-2-yunqiang.su@cipunited.com \
--to=yunqiang.su@cipunited.com \
--cc=binutils@sourceware.org \
--cc=macro@orcam.me.uk \
/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).