Retrospectively Reverse-Engineering Apple's Neural Engine
A developer has retrospectively reverse-engineered the Apple Neural Engine (ANE) on the M1 chip to map its internal architecture after abandoning earlier efforts to create a Linux driver. The analysis reveals that the ANE's design was heavily optimized for CNN-era workloads with predictable data reuse patterns, making it less suitable for modern transformer models. The M5 chip's integration of ANE cores into the GPU marks a significant shift, effectively signaling the end of the standalone NPU as a distinct hardware component.
- ▪The M1 ANE consists of 16 parallel compute cores, each containing 128 FP16 or 256 INT8 multiply-accumulate lanes for a total of 2048 parallel lanes.
- ▪The hardware architecture was specifically designed to exploit predictable data reuse patterns found in convolutional neural networks, which limits its efficiency for autoregressive transformer decoding.
- ▪Apple's M5 chip integrates ANE cores directly within the GPU cores, a move that indicates the transition away from standalone neural processing units.
- ▪The reverse-engineering effort focused on mapping the compute, datapath, scheduler, and memory structures to understand Apple's historical assumptions about ML workloads.
- ▪Previous attempts to build a general-purpose Linux driver for the ANE were abandoned because the hardware's opinionated architecture did not support a broad class of workloads.
Hacker News (Front Page) files mainly under programming. We currently carry 1,505 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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 publisher | Hacker News (Front Page) |
| Canonical URL | https://eiln.github.io/posts/ane.html |
| Publication time | Sat, 12 Sep 2026 07:54:03 +0000 |
| Retrieval time | 2026-09-12T08:12:51.011Z |
| Last seen | 2026-09-12T08:12:51.011Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | NmwnwsoCzqoH · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
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
Retrospectively Reverse-Engineering Apple's Neural EngineAug 10, 2026(5089 words)I stopped working on the reverse-engineered Apple Neural Engine (ANE) driver three years ago, upon a sad mini realization that the ANE block is just not that useful, and I could be doing more useful things, and moved onto upstreaming other, more useful, blocks. The ANE's architecture was too opinionated to build a general-purpose accelerator platform around it, and a linux driver effectively opening ANE hardware API access could not broaden the class of workloads it could do.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (Front Page).
Discussion
0 commentsMore from Hacker News (Front Page)
