[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] d9345f: target/m68k: correctly disassemble mo

From: GitHub
Subject: [Qemu-commits] [qemu/qemu] d9345f: target/m68k: correctly disassemble move16
Date: Mon, 02 Jul 2018 06:56:43 -0700

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: d9345f1e1b1936b9ed7026b83091cf701f7ce07e
  Author: Laurent Vivier <address@hidden>
  Date:   2018-07-02 (Mon, 02 Jul 2018)

  Changed paths:
    M disas/m68k.c

  Log Message:
  target/m68k: correctly disassemble move16

"move16 address@hidden,%a1@" and "fmovel (cpid=3) address@hidden,%fpcr"
share the same opcode.

To fix that, backport the fix from binutils:

  2005-11-10  Andreas Schwab  <address@hidden>

     * m68k-dis.c (print_insn_m68k): Only match FPU insns with
     coprocessor ID 1.

Reported-by: Thomas Huth <address@hidden>
Signed-off-by: Laurent Vivier <address@hidden>
Tested-by: Thomas Huth <address@hidden>
Message-Id: <address@hidden>

  Commit: 2d58e33ec1b76990f09bc1e3412e0b36e1ac4634
  Author: Peter Maydell <address@hidden>
  Date:   2018-07-02 (Mon, 02 Jul 2018)

  Changed paths:
    M disas/m68k.c

  Log Message:
  Merge remote-tracking branch 'remotes/vivier/tags/m68k-for-3.0-pull-request' 
into staging

Fix move16 instruction disassembly

# gpg: Signature made Mon 02 Jul 2018 11:25:51 BST
# gpg:                using RSA key F30C38BD3F2FBE3C
# gpg: Good signature from "Laurent Vivier <address@hidden>"
# gpg:                 aka "Laurent Vivier <address@hidden>"
# gpg:                 aka "Laurent Vivier (Red Hat) <address@hidden>"
# Primary key fingerprint: CD2F 75DD C8E3 A4DC 2E4F  5173 F30C 38BD 3F2F BE3C

* remotes/vivier/tags/m68k-for-3.0-pull-request:
  target/m68k: correctly disassemble move16

Signed-off-by: Peter Maydell <address@hidden>

Compare: https://github.com/qemu/qemu/compare/646f34fa5482...2d58e33ec1b7
      **NOTE:** This service been marked for deprecation: 

      Functionality will be removed from GitHub.com on January 31st, 2019.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]