[Top][All Lists]

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

[Bug binutils/25224] New: [Z80] Add support for Zylog Z180 and eZ80 CPUs

From: sergey.belyashov at gmail dot com
Subject: [Bug binutils/25224] New: [Z80] Add support for Zylog Z180 and eZ80 CPUs
Date: Mon, 25 Nov 2019 10:31:03 +0000


            Bug ID: 25224
           Summary: [Z80] Add support for Zylog Z180 and eZ80 CPUs
           Product: binutils
           Version: 2.34 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: sergey.belyashov at gmail dot com
  Target Milestone: ---

Created attachment 12091
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12091&action=edit
Add support for GBZ80, Z180, and eZ80 to bfd/gas/binutils

There is archive with 3 patches (bfd, disassembler, gas), which add full
support for Zylog Z180 and EZ80 CPUs to Z80 arch.
Summary changes:
1. Due to limited number of COFF flags used to identify MACH earlier mask
configuration were changes to enumeration. Old values for bfd_mach_z80* are
kept. 2. Support for GBZ80 (Game Boy Z80 - Z80 with reduced instruction set) is
in initial state, may be later be completed by some one.
3. Undocumented instructions may be enabled/disabled on per target basis, i.e.
you may enable SLI instruction for EZ80, but not all "unportable" instructions.
4. Number of dump columns is increased (longest EZ80 instruction is 6 bytes).

I suggest to completely remove z80strict and z80full maches:

bfd_mach_z80 - Z80 with some undocumented instructions (common for Z80 and
bfd_mach_z80strict - Z80 with documented instructions only
bfd_mach_z80full - Z80 with all undocumented instructions

Classic Zylog Z80 supports all undocumented instructions. Later CPUs may
support or not them, but in most cases them have new instructions, so new mach
is required.

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

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