From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] MIPS: Fix binutils-all tests for r6 triples
Date: Mon, 13 Nov 2023 15:58:18 +0000 (GMT) [thread overview]
Message-ID: <20231113155818.388A03858C2F@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=94c641840b4a0ed873db311a7b907ec4dd99cb33
commit 94c641840b4a0ed873db311a7b907ec4dd99cb33
Author: YunQiang Su <yunqiang.su@cipunited.com>
Date: Mon Nov 13 15:58:03 2023 +0000
MIPS: Fix binutils-all tests for r6 triples
Diff:
---
binutils/testsuite/binutils-all/mips/mips16-extend-noinsn.d | 3 ++-
binutils/testsuite/binutils-all/mips/mixed-mips16-micromips.d | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/binutils/testsuite/binutils-all/mips/mips16-extend-noinsn.d b/binutils/testsuite/binutils-all/mips/mips16-extend-noinsn.d
index 41bb49e6ac7..dd20fc121a2 100644
--- a/binutils/testsuite/binutils-all/mips/mips16-extend-noinsn.d
+++ b/binutils/testsuite/binutils-all/mips/mips16-extend-noinsn.d
@@ -1,8 +1,9 @@
#PROG: objcopy
+#as: -march=from-abi
#objdump: -d --prefix-addresses --show-raw-insn
#name: MIPS16 unsupported EXTEND and undefined opcode disassembly
-# Verify raw hexadecimal EXTEND and inexistent opcode disassembly.
+# Verify raw hexadecimal EXTEND and unexistent opcode disassembly.
.*: +file format .*mips.*
diff --git a/binutils/testsuite/binutils-all/mips/mixed-mips16-micromips.d b/binutils/testsuite/binutils-all/mips/mixed-mips16-micromips.d
index 4a53dfb8578..65459d510d3 100644
--- a/binutils/testsuite/binutils-all/mips/mixed-mips16-micromips.d
+++ b/binutils/testsuite/binutils-all/mips/mixed-mips16-micromips.d
@@ -1,4 +1,5 @@
#PROG: objcopy
+#as: -march=from-abi
#objdump: -drt
#name: Mixed MIPS16 and microMIPS disassembly
reply other threads:[~2023-11-13 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231113155818.388A03858C2F@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-cvs@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).