AN OPEN-SOURCE RUST PROJECT

Classic BASIC.
New foundations.

A modern compiler and runtime for Amiga GFA BASIC 3.5 — researched carefully, built in Rust, and designed for native Linux executables.

Experimental · Early development · Not production-ready
factorial.basGFA BASIC 3.5
01x = FACT(5)
02PRINT x
03
04' Output from the narrow prototype
› 120
compiler prototypeRust · native build
RUST✳GFA BASIC 3.5✳LLVM — PLANNED✳LINUX X86-64✳OPEN SOURCE✳RUST✳GFA BASIC 3.5
MAINTAINER VIEW · REPOSITORY DATA

Implementation dashboard.

A source-linked snapshot of what exists today and what remains planned. Research, prototypes and supported implementation are deliberately kept separate.

Project maturityexperimentalExperimental project
Product targetLinux x86-64Amiga GFA BASIC interpreter 3.5
Workspace4Rust crates in Cargo workspace

Implemented 3.5 addendum API

Fully implemented declarations0 / 33

Explicitly documented interpreter declarations from the Amiga 3.5 addendum only; includes language-core and Amiga platform declarations. Excludes inherited 3.0 base-manual features, editor-only changes, compiler-only features, and Atari ST declarations. This is a confirmed addendum subset, not the complete Amiga GFA BASIC 3.5 language API.

Roadmap progress

Phase 0 · Maintain a trustworthy project baseline10/10 · 100%
Phase 1 · Establish an evidence-backed first language subset1/8 · 12%
Phase 2 · Build a minimal vertical compiler slice1/12 · 8%
Phase 3 · Add platform APIs and robustness1/7 · 14%
Phase 4 · Release readiness4/13 · 31%

Implementation states

Build-time snapshot · Source freshness is not timestamped in the current data model. Status model ↗ · Detailed roadmap ↗

REPOSITORY · DELIVERY HISTORY

Recent activity.

Recently updated

  1. Merged pull request[API Registry] Reconcile Amiga GFA BASIC 3.5 platform profile ↗PR #607 merged
  2. Commit[API Registry] Reconcile Amiga GFA BASIC 3.5 platform profile (#607) ↗Commit 55e536a
  3. Merged pull requestdocs: define Ghidra API analysis boundary for agents ↗PR #612 merged
  4. Commitdocs: define Ghidra API analysis boundary for agents (#612) ↗Commit e5813bf
  5. Merged pull request[Compiler] Lower typed IR from resolved semantic model ↗PR #601 merged
  6. Commit[Compiler] Lower typed IR from resolved semantic model (#601) ↗Commit ced5ad4
  7. Merged pull request[CI] Make mutation schedule guard resilient to delayed runners ↗PR #609 merged
  8. Commit[CI] Make mutation schedule guard resilient to delayed runners (#609) ↗Commit f020422
  9. Merged pull request[CI] Suppress ShellCheck false positive for Pages cleanup trap ↗PR #606 merged
  10. Commitci: suppress ShellCheck false positive for EXIT cleanup trap (#606) ↗Commit e591114
  11. Merged pull request[Testing] Validate and select versioned construct manifests (#571) ↗PR #593 merged
  12. Commit[Testing] Validate and select versioned construct manifests (#571) (#593) ↗Commit 7eb80ca

Last successful source fetch: · Maximum 12 items · GitHub PR merges and commits are activity events, not feature-completion claims.

MAINTAINER VIEW · GITHUB ACTIONS

CI & supply-chain health.

Build-time snapshot from GitHub Actions. Latest result and last successful run are shown separately; missing runs, stale results and unconfigured workflows are never counted as healthy.

Benchmarks

SUCCESS

Latest: success · pull_request · worker/issue-42-data-pointer-fixture · 0h ago · fresh

Last success: 2026-11-21T22:21:22Z · 0h ago · Open successful run ↗

Source-loading benchmark; pull requests validate compilation without recording measurements.

Release SBOM

SUCCESS

Latest: success · pull_request · worker/issue-42-data-pointer-fixture · 0h ago · fresh

Last success: 2026-11-21T22:22:00Z · 0h ago · Open successful run ↗

Validates PR SBOMs and uploads on published releases; release attachment is unproven until a release runs.

Conformance suite

NOT CONFIGURED

No workflow run recorded

No successful run recorded

No dedicated compiler conformance workflow is configured.

Snapshot generated 2026-11-21T22:23:13.231922Z. Freshness threshold: 168 hours. View all workflow runs ↗

01 / THE PROJECT

Bringing a classic
language forward.

GFA BASIC was part of the creative computing era of the Amiga. This project explores a careful, evidence-led way to compile its 3.5 dialect into native programs — without pretending that the hard compatibility work is already done.

01

Faithful by evidence

Language rules are tied to version-specific references. Uncertain behavior stays explicitly unresolved.

02

Native by design

The target is Linux x86-64. LLVM is the planned production backend; the current C bridge is temporary.

03

Rust throughout

A modular compiler, generated-program runtime and platform layer form the planned foundation.

02 / WHAT WORKS TODAY

A small step.
A real executable.

The experimental frontend accepts a deliberately narrow, documented subset: literal FACT, VARIAT and COMBIN assignments followed by PRINT. It verifies typed project IR before using a temporary C/cc bootstrap.

Build instructions in the README ↗
SUPPORTED SHAPE · ILLUSTRATIVE
x = FACT(5)
PRINT x
BUILD OUTPUT Native executable
!

The current prototype demonstrates a deliberately limited subset; it is not general GFA BASIC support and does not claim compatibility with the original interpreter. Variables are limited to x, y and z, with no reassignment. Arguments must be integer literals: FACT(n) accepts 0–20, while VARIAT(n,k) and COMBIN(n,k) accept 0 ≤ k ≤ n ≤ 20. These are prototype limits, not limits of the GFA BASIC language. General language semantics, the production IR, LLVM backend and runtime remain unimplemented.

03 / DEVELOPER TOOLS

Early tools.
Explicit boundaries.

IMPLEMENTED SUBSET

Source formatter

The gfabasic fmt library and CLI format only the currently supported FACT, VARIAT, COMBIN and PRINT syntax. Unsupported syntax is rejected; this is not yet a general GFA BASIC formatter.

↗
INITIAL LSP

Language server

The standalone LSP adapter supports document open/change/close and parser diagnostics. Formatting integration, navigation, completion and rename are not implemented.

↗
PROJECT STATUS

Research before claims

Language rules remain evidence-gated against the Amiga 3.5 references. The implemented editor tools do not imply full language parsing or conformance.

↗
04 / ARCHITECTURE

Clear boundaries.
Independent layers.

The planned system separates language semantics from code generation and platform integration. Each layer can evolve without quietly changing the compatibility contract.

01
⌘

Compiler

Source loading, diagnostics and a narrow FACT/PRINT frontend with prototype-only typed IR. General semantic analysis and IR remain planned.

EXPERIMENTAL CORE
→
→
03
▤

Runtime & platform

Generated-program runtime and Linux integration, including planned SDL3 support.

PLANNED
FIXED PRODUCT TARGETAmiga GFA BASIC interpreter 3.5→Linux x86-64 · ELF · GNU ABI
05 / API CATALOGUE

What the language defines.

A generated, source-linked inventory of GFA BASIC declarations. Evidence, implementation, Linux support and conformance are shown separately; unknown and disputed behavior stays visible.

Coverage counts are independent and have explicit denominators. There is no aggregate “percent implemented”. Select an entry to open its source-linked project documentation.

Loading the generated API catalogue…

06 / THE ROAD AHEAD

Built in deliberate stages.

Dependencies & sequencing rules

The initial dialect/version is selected (Amiga GFA BASIC interpreter 3.5); 3.0/3.03 rules remain inherited candidates until confirmed for 3.5, and feature-level source evidence still gates language semantics, parser acceptance criteria, and conformance claims.

Source manager, lexer, parser, semantic analysis and typed IR are sequential dependencies for the first compiler path.

LLVM backend and runtime integration depend on a stable typed IR and runtime ABI.

Platform APIs depend on verified profile declarations; Amiga and Atari ST evidence must not be conflated.

A user quick start and installation guide depend on a working, tested CLI and distributable build.

The generic source-loader fuzz target is implemented; lexer/parser fuzz targets depend on stable frontend entry points and source contracts.

Release packaging depends on successful end-to-end builds and explicit runtime dependency policy.

Read the detailed roadmap ↗
07 / EXPLORE

Go a little deeper.

G
OPEN SOURCE · BUILT IN THE OPEN

Help shape what comes next.

Follow the work, inspect the code, or contribute to the research and implementation.

View repository ↗