Home · Browse · Instruction List

Instruction List

1 program Added 2025-11-12T11:36:44Z Model: google/gemini-2.5-proTemp: 0.4 Evidence Report issue View issues

Aliases: IL

Provenance: commit f962973e7d · authored 2025-11-12T12:36:44+01:00 · model google/gemini-2.5-pro

Sources mentioning this language

3 sources · pl_id: pl/instruction-list-2

LLM (this repo) · 1 Wikipedia Wikidata · Q613332

Related languages

AWL (0.50)Quil (0.31)ASIC (0.25)ISLE (0.25)ISPS (0.23)

Real programs from Software Heritage

No SWH evidence indexed yet for this language. (Either the SWH mining hasn't reached this language's extensions, or no matching files exist in the archive.)

Programs collected by LLM agents experimental · unverified

Gathered by LLM agents during the experiment that started this catalogue. They are not verified: the agent names an origin, but a program can be altered or invented — an audit found one attributed to a file that does not exist, in a syntax the language does not have. Prefer the programs archived by Software Heritage above. The catalogue's goal is the languages themselves, grounded in sources (PLDB, Wikipedia, Rosetta Code, …), with real archived programs; these examples may be dropped.

FOR loop in Instruction List

Origin · Download · manifest.json · Report

Provenance: commit f962973e7d · authored 2025-11-12T12:36:44+01:00 · model google/gemini-2.5-pro · Temp 0.4

code.il · added: 2025-11-12T11:36:44Z

LD 1
ST Index
Loop:
LD Index
LE 10
JMPC EndLoop
LD Result
ADD Index
ST Result
LD Index
ADD 1
ST Index
JMP Loop
EndLoop:

Contribute — propose a file extension

Tell us where to find evidence about Instruction List (mapped to pl/instruction-list-2). A reference URL is required; at least one of extension or program code must be provided too. A maintainer reviews each submission via a draft PR before anything lands.

File extension (optional) — e.g. .oak. Some PLs (e.g. esolangs) have no convention; leave empty if so. Friendly name (optional)

Reference URL * — public URL where the extension is used (GitHub file, GitLab, spec page, …) Notes (optional) — 1–3 sentences if context helps the maintainer

Optional: attach a program from that URL

If the reference URL points at a single source file you'd like to add as an example program, paste it below. The workflow will write it under languages/Instruction List/programs/<sha>/. Keep under ~200 lines.

Title (optional) — e.g. "Factorial", "Quicksort" License guess (optional) — MIT, GPL-2.0, …

Code (optional) — paste verbatim bytes from the reference URL

(or open the pre-filled issue directly)