WeSearch

6502 Emulator Runs 1 Instruction/S (Written in Markdown, Running in an LLM)

adam· ·14 min read · 0 reactions · 0 comments · 37 views
6502 Emulator Runs 1 Instruction/S (Written in Markdown, Running in an LLM)
TL;DR · WeSearch summary

A new experiment explores the implementation of a 6502 microprocessor emulator using Markdown, executed with OpenCode and the GLM 5.1 model. The 6502 was a widely used microprocessor in the 1980s, known for its simplicity and efficiency. This emulator runs by fetching opcodes and executing them, showcasing a unique approach to utilizing LLMs as processors.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
Adam Dunkels · adam
Read full at Adam Dunkels →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherAdam Dunkels
Canonical URLhttps://dunkels.com/adam/llm-6502-emulator/
Publication timeMon, 25 May 2026 11:14:54 +0000
Retrieval time2026-05-25T11:37:36.700Z
Last seen2026-05-25T11:37:36.700Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Clusterlkv7HGgYbAyo
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

In previous posts we explored what happens if we treat LLMs as processors that run Markdown as their machine code: a user-space IP stack written in Markdown and a BASIC interpreter written in Markdown. Today we are going to look at an emulator for a 6502 microprocessor written in Markdown and executed with OpenCode and the GLM 5.1 model running on Grunden.ai. Yes, this is a ridiculous idea with no practical value. But it is a fun experiment. A 6502 Microprocessor Written in Markdown The 6502 microprocessor was a popular microprocessor for home computers in the 1980s. It was used in the Commodore 64, Apple II, Nintendo Entertainment System , among many others. The 6502 microprocessor has three built-in registers (A, X, and Y) and can address a memory range of 64k.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Adam Dunkels.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Adam Dunkels