From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: qemu-devel@nongnu.org
Cc: laurent@vivier.eu,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: [Qemu-devel] [PATCH 1/2] m68k: Fix opcode mask for fbcc instruction
Date: Wed, 3 Feb 2016 10:37:00 +0100 [thread overview]
Message-ID: <1454492221-30625-2-git-send-email-glaubitz@physik.fu-berlin.de> (raw)
In-Reply-To: <1454492221-30625-1-git-send-email-glaubitz@physik.fu-berlin.de>
Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
---
target-m68k/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-m68k/translate.c b/target-m68k/translate.c
index 342c040..535d7f9 100644
--- a/target-m68k/translate.c
+++ b/target-m68k/translate.c
@@ -2940,7 +2940,7 @@ void register_m68k_insns (CPUM68KState *env)
INSN(shift_reg, e0a0, f0f0, CF_ISA_A);
INSN(undef_fpu, f000, f000, CF_ISA_A);
INSN(fpu, f200, ffc0, CF_FPU);
- INSN(fbcc, f280, ffc0, CF_FPU);
+ INSN(fbcc, f280, ff80, CF_FPU);
INSN(frestore, f340, ffc0, CF_FPU);
INSN(fsave, f340, ffc0, CF_FPU);
INSN(intouch, f340, ffc0, CF_ISA_A);
--
2.7.0
next prev parent reply other threads:[~2016-02-03 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 9:36 [Qemu-devel] m68k: More bug fixes for translation code John Paul Adrian Glaubitz
2016-02-03 9:37 ` John Paul Adrian Glaubitz [this message]
2016-02-03 9:38 ` [Qemu-devel] [PATCH 1/2] m68k: Fix opcode mask for fbcc instruction Laurent Vivier
2016-02-08 23:13 ` John Paul Adrian Glaubitz
2016-02-03 9:40 ` John Paul Adrian Glaubitz
2016-02-03 9:42 ` Laurent Vivier
2016-02-03 9:37 ` [Qemu-devel] [PATCH 2/2] m68k: Build the opcode table only once to avoid multithreading issues John Paul Adrian Glaubitz
2016-02-03 9:39 ` Laurent Vivier
2016-02-03 9:57 ` Laurent Vivier
2016-02-03 10:06 ` John Paul Adrian Glaubitz
2016-02-03 10:13 ` Laurent Vivier
2016-02-03 10:17 ` John Paul Adrian Glaubitz
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=1454492221-30625-2-git-send-email-glaubitz@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).