Skip to main content

upeepz80 - Universal Peephole Optimizer for Z80

A language-agnostic peephole optimization library for Z80 compilers that generate pure Z80 assembly.

Overview

upeepz80 provides high-quality optimization passes for compilers targeting the Zilog Z80 processor. Unlike upeep80, this library expects pure Z80 mnemonics in lowercase as input (ld, jp, jr, etc.) and produces optimized Z80 assembly output with lowercase mnemonics.

If your compiler generates 8080 mnemonics (MOV, MVI, LXI, etc.) that need translation to Z80, use upeep80 instead.

Features

Peephole Optimizations

  • Pattern-based optimization on Z80 assembly
  • Redundant load/store elimination
  • Jump optimization (jp to jr conversion, jump threading)
  • djnz conversion (dec b; jr nz → djnz)
  • Stack operation combining (push/pop to ld conversions)
  • Dead store elimination
  • Tail call optimization (call x; ret → jp x)
  • Register copy optimization (push hl; pop de → ld d,h; ld e,l)

Z80-Specific Features

  • Relative jump optimization (jp → jr where in range)
  • djnz loop optimization
  • Z80 block instruction awareness
  • Direct ld de,(addr) usage (Z80-only instruction)

Installation

pip install upeepz80

Or for development:

git clone https://github.com/avwohl/upeepz80.git
cd upeepz80
pip install -e ".[dev]"

Usage

Basic Usage

from upeepz80 import optimize

# Optimize Z80 assembly code
assembly = """
    ld a,0
    or b
    push hl
    pop de
    jp LABEL
LABEL:
    ret
"""

optimized = optimize(assembly)
print(optimized)
# Output:
#     xor a          ; ld a,0 → xor a (smaller): or b sets the flags xor a changes
#     or b
#     ld d,h         ; push/pop → register moves (faster)
#     ld e,l
# LABEL:
#     ret            ; jp to next instruction eliminated

Without the or b, ld a,0 stays: xor a also sets the flags, and the caller this code returns to might read them.

Using the Optimizer Class

from upeepz80 import PeepholeOptimizer

# Create optimizer
optimizer = PeepholeOptimizer()

# Optimize assembly code
optimized_asm = optimizer.optimize(assembly_text)

# Check statistics
print(f"xor a conversions: {optimizer.stats.get('zero_a_ld', 0)}")
print(f"Jump threading: {optimizer.stats.get('jump_thread', 0)}")
print(f"djnz conversions: {optimizer.stats.get('djnz', 0)}")

Optimization Phases

The optimizer runs multiple phases:

  1. Pattern Matching and Z80-Specific Optimizations - peephole patterns and inline rewrites, repeated until nothing changes (up to 10 passes)
  2. Jump Threading - Thread through intermediate jumps
  3. Pattern Matching once more, for what threading exposed
  4. Dead Store Elimination - Remove a parameter's store at procedure entry when nothing reads it, to storage the module defines and does not export
  5. Relative Jumps - Convert jp to jr, and dec b; jp nz to djnz, where the target is in reach; last, because it counts bytes

Correctness

A rewrite that changes what a register or flag holds afterwards is made only where nothing reads the old value. ld a,0 → xor a changes every flag, so it is made only where the flags are overwritten before they are read; ld hl,5 / ld a,l → ld a,5 leaves HL as it was, so it is made only where HL is. The optimizer knows what each Z80 instruction reads and writes (upeepz80/z80.py), and follows every path from the rewritten code: on, into both arms of a branch, round loops, into a routine the text calls and back, from a ret to every call of the routine, and through a push to its pop. A path that leaves what the text shows counts as reading everything: a call or jump to a label defined elsewhere, call 5, jp 0, jp (hl), data, or the end of the text. So does a ret from a routine that another module may call (public, NAME::, or its address taken), or that takes its return address off the stack (ex (sp),hl / ret).

Numbers are read under the text's radix. Where it sets a .radix other than ten, only numbers that mean the same under any radix are rewritten.

Every rewrite writes only instructions the Z80 has, and a relative jump is made only where its target is known to be within reach, counting bytes.

tests/peepfuzz.py checks this: it generates random programs around every shape the optimizer rewrites, runs each before and after optimization on a Z80 interpreter (tests/z80sim.py, itself checked against a real Z80 core by tests/simcheck.py), and compares every register, flag and byte of memory.

Architecture

upeepz80 is designed to be language-agnostic:

  • Works directly on Z80 assembly text
  • No knowledge of source language required
  • Pattern-based transformation engine
  • Zero runtime dependencies

Comparison with upeep80

Feature upeep80 upeepz80
Input 8080 or Z80 mnemonics Z80 mnemonics only
Output Z80 or 8080 (configurable) Z80 only
Translation 8080 → Z80 translation None needed
Use case Compilers generating 8080 code Compilers generating Z80 code

Choose upeepz80 if your compiler already generates Z80 mnemonics. Choose upeep80 if your compiler generates 8080 mnemonics.

Used By

  • uplm80 - PL/M-80 compiler for Z80 (after migration)
  • uada80 - Ada compiler for Z80 (after migration)

Development

Running Tests

pytest

Type Checking

mypy upeepz80

Code Formatting

black upeepz80
ruff check upeepz80

Performance

Benchmarks on typical compiler workloads:

  • Peephole optimization: ~50,000 instructions/second
  • Memory usage: Minimal (pattern-based, no large data structures)

Contributing

Contributions are welcome. Open an issue or a pull request.

License

This project is licensed under the GNU General Public License v2.0 - see LICENSE for details.

History

upeepz80 is a sibling project to upeep80, designed for compilers that generate native Z80 assembly. It shares the same optimization algorithms but removes the 8080 translation layer for cleaner, more efficient code when 8080 support isn't needed.

  • 80un - Unpacker for the CP/M archive and compression formats LBR, ARC, squeeze, crunch, and CrLZH.
  • cpmdroid - Z80/CP/M emulator for Android phones and tablets. It emulates the RomWBW HBIOS interface and a VT100 terminal.
  • cpmemu - Z80/CP/M emulator for Linux and Windows, with Z80 and 8080 CPU cores. It translates the BDOS and BIOS calls of CP/M 2.2 programs to the host file system.
  • ioscpm - Z80/CP/M emulator for iOS and macOS. It emulates the RomWBW HBIOS interface and runs CP/M 2.2 and CP/M 3.
  • learn-ada-z80 - Collection of more than 90 Ada example programs for uada80, the Ada compiler for the Z80 processor and CP/M.
  • mbasic - Python interpreter for MBASIC 5.21, the Microsoft BASIC-80 for CP/M. Two compiler backends compile the programs to CP/M .COM files or to JavaScript.
  • mbasic2025 - Reconstruction of the lost source code of MBASIC 5.21, the Microsoft BASIC-80 for CP/M. The MACRO-80 source code assembles to a binary that matches mbasic.com byte for byte.
  • mbasicc - C++17 interpreter for MBASIC 5.21, the Microsoft BASIC-80 for CP/M. It runs on Linux and macOS.
  • mbasicc_web - Web browser interpreter for MBASIC 5.21, the Microsoft BASIC-80 for CP/M. Emscripten compiles the mbasicc interpreter to WebAssembly.
  • mpm2 - Z80 emulator for MP/M II, the multi-user CP/M operating system. Users connect over SSH, and SFTP clients transfer files.
  • romwbw_emu - Hardware-level Z80/CP/M emulator for Linux and macOS. It emulates the RomWBW HBIOS interface and switches banks in 512 KB of ROM and 512 KB of RAM.
  • scelbal - Floating-point BASIC interpreter for the 8080 processor and CP/M. A translator converts the original 8008 source code to 8080 source code.
  • uada80 - Ada compiler for the Z80 processor and CP/M 2.2. It compiles a subset of Ada 2012 to CP/M .COM files.
  • uc80 - C compiler for the Z80 processor and CP/M. It optimizes for small code size.
  • ucow - Cowgol compiler for the Z80 processor and CP/M. It runs on Linux in Python.
  • um80_and_friends - Linux toolchain that is compatible with Microsoft MACRO-80. It has an assembler, a linker, a librarian, and a disassembler.
  • uplm80 - PL/M-80 compiler for the Z80 processor and CP/M. It writes Intel 8080 and Zilog Z80 assembly language.
  • z80cpmw - Z80/CP/M emulator for Windows. It emulates the RomWBW HBIOS interface and boots CP/M from disk images.

See Also

Release files for upeepz80 0.2.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for upeepz80 0.2.5
File Size Uploaded
upeepz80-0.2.5.tar.gz 61.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for upeepz80 0.2.5
File Interpreter ABI Platform
upeepz80-0.2.5-py3-none-any.whl Python 3 none any Details

Total release size: 105.7 kB

Release files / upeepz80-0.2.5.tar.gz

Download URL upeepz80-0.2.5.tar.gz
Size 61.5 kB
Tags Source
SHA-256 checksum
How to use checksums
87e1cff08f2d56bc3d12a9da68096fff5261d111ab888e69639860677a9d29b4
BLAKE2b-256 checksum
How to use checksums
ecfc44a31013f2aa6075c1c87953a3e087d41efde33ae84aa2bb6db499f2bc8c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / upeepz80-0.2.5-py3-none-any.whl

Download URL upeepz80-0.2.5-py3-none-any.whl
Size 44.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6cb4abfb5b8a38b2daf32068522a158a62d9b3d5b7d97909a7f3d8f440e38f88
BLAKE2b-256 checksum
How to use checksums
d76ae56faf72f086d5da2da941095ba954993c87128ef06ba5eef01c207db90f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.5 This release

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page