From: Jan Beulich <jbeulich@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] x86: adjust an ILP32 testcase using .insn
Date: Thu, 20 Apr 2023 09:26:19 +0000 (GMT) [thread overview]
Message-ID: <20230420092619.DA6373858D37@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b6b746e6b81c69588d7ca07708b307bd7728b0ac
commit b6b746e6b81c69588d7ca07708b307bd7728b0ac
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Apr 20 11:26:10 2023 +0200
x86: adjust an ILP32 testcase using .insn
In commit 6967633c8b49 ("x86: convert testcases to use .insn") an ILP32
clone of a testcase was missed in the set of tests needing --divide
added.
Reported-by: Clément Chigot <chigot@adacore.com>
Diff:
---
gas/testsuite/gas/i386/ilp32/x86-64-opcode.d | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gas/testsuite/gas/i386/ilp32/x86-64-opcode.d b/gas/testsuite/gas/i386/ilp32/x86-64-opcode.d
index bd67122cc18..3dc83047739 100644
--- a/gas/testsuite/gas/i386/ilp32/x86-64-opcode.d
+++ b/gas/testsuite/gas/i386/ilp32/x86-64-opcode.d
@@ -1,5 +1,5 @@
#source: ../x86-64-opcode.s
-#as: -J
+#as: -J --divide
#objdump: -drw
#name: x86-64 (ILP32) opcode
#dump: ../x86-64-opcode.d
reply other threads:[~2023-04-20 9:26 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=20230420092619.DA6373858D37@sourceware.org \
--to=jbeulich@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).