Machine Learning · 2026-11-06

Loopback Transformer: Towards a Unified View of Residual Looped Transformers

arXiv:2611.07226v1 Announce Type: new Abstract: Looped Transformers reduce parameter count by repeatedly applying shared blocks, but parameter sharing alone does not determine how the results of repeated computation are reused. We take the depth-memory view of residual connections and analyze which representation is stored after each block application and how later reads weight it.

SHARE THIS ARTICLE LinkedIn X Facebook

arXiv:2611.07226v1 Announce Type: new Abstract: Looped Transformers reduce parameter count by repeatedly applying shared blocks, but parameter sharing alone does not determine how the results of repeated computation are reused. We take the depth-memory view of residual connections and analyze which representation is stored after each block application and how later reads weight it. A full block output contains both its input and its new update, so weighting that output also reweights the history already carried by the input. Reading individual updates instead, with the shared stack's input kept on a separate path, gives separate controls over input strength, total update weight, and allocation across updates.

Source and attribution

Original source: arXiv ML ↗

This is an attributed editorial digest. For the complete study and original reporting, follow the source link.

Reader feedback

0 likes · 0 dislikes

Sign in to like or dislike this research.

SHARE THIS ARTICLE LinkedIn X Facebook
← Back to research archive