Skip to content

[block] Clarify scalar body entry in Tile blocks - #273

Merged
zhoubot merged 1 commit into
mainfrom
codex/tile-scalar-body-bstart
Sep 12, 2026
Merged

zhoubot merged 1 commit into
mainfrom
codex/tile-scalar-body-bstart

Conversation

@zhoubot

@zhoubot zhoubot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Clarify PTO-REQ-SCALAR-BODY-ENTRY-001 that the first decoded scalar instruction may enter the body of any active block kind, explicitly including Tile blocks.
  • Preserve the active Tile block kind during scalar body entry.
  • Add an executable AVS point with no intervening C.BSTART.STD.

This closes documentation/evidence around the behavior already accepted by issue #191 and ADR-BLOCK-0012. It changes no instruction encoding, decoder, block state, or execution transition.

Validation

  • make pr-check: 10/10 PASS
  • exact focused ASL matrix selected by scripts/prepare-pr: 17/17 PASS
  • new Tile-block scalar-body AVS: PASS
  • git diff --check: PASS

Independent exact-input review remains required before merge, as reported by scripts/prepare-pr.

Downstream implementation: LinxISA/llvm-project#92. LinxISA implementer guidance: LinxISA/linx-isa#201.

Make the existing PTO-REQ-SCALAR-BODY-ENTRY-001 contract explicit that decoded scalar instructions may enter the body of an active Tile block without an intervening Standard BSTART. Add focused executable evidence that body entry preserves the Tile block kind.

This clarifies the accepted issue #191 / ADR-BLOCK-0012 behavior and changes no encoding or state transition.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant