PTO-ARCH-DATA-TYPES-MEMORY-OPERATIONSThe complete ASL owner is shown directly below.
// PTO-UNIT: {"id":"PTO-ARCH-DATA-TYPES-MEMORY-OPERATIONS","surface":"arch","classification":["data-types","memory-operations"],"depends_on":["PTO-ARCH-DATA-TYPES-MEMORY-MODEL"]}type AddressUpdateMode of enumeration { AddressUpdate_None, AddressUpdate_PreIndex, AddressUpdate_PostIndex};
type AtomicOperation of enumeration { Atomic_SWAP, Atomic_ADD, Atomic_AND, Atomic_OR, Atomic_XOR, Atomic_SMIN, Atomic_SMAX, Atomic_UMIN, Atomic_UMAX};
This unit names the address-update and atomic-operation selectors shared by scalar and tile memory execution.
Keeping these selectors in one owner prevents individual instructions from inventing incompatible names for the same operation class.
AddressUpdateMode has AddressUpdate_None, AddressUpdate_PreIndex, and AddressUpdate_PostIndex.AtomicOperation covers swap, add, bitwise AND/OR/XOR, signed min/max, and unsigned min/max.Pre-index and post-index are distinct selectors. The consuming instruction owner determines when the base update is computed and committed.
Signed and unsigned min/max have separate enum members: Atomic_SMIN, Atomic_SMAX, Atomic_UMIN, and Atomic_UMAX.
No enum member implies fault, ordering, size, or publication rules; those remain parameters and behavior of the consuming owner.
This unit has no fallback or implementation-defined selector. A decoder must map only to a declared member before execution.
Selector identity is portable, while support and legality for a particular instruction form remain with that instruction's current ASL owner.
An atomic instruction selecting Atomic_ADD still needs its own address, width, order, fault, and commit contract; this enumeration contributes only the operation identity.
Likewise, AddressUpdate_PostIndex identifies the mode but does not by itself state whether a failed access updates the base register.
Bodies come from owning ASL. Dragging or buttons change only this page-session view order.
No NDF clause is attached to this unit.
6 matching entries
PTO-AVS-ARCH-DATA-TYPES-MEMORY-OPERATIONS-STATIC-001tests/asl/arch/data-types/memory-operations/arch-static-memory-operations-contract-001.asl8b451f6f410d2e40e83e06f6b9c7509dd4e7a4f9bf9784c4926ef52316f7149cPTO-EVIDENCE-RELEASE-TRACEABILITYPTO-EVIDENCE-RELEASE-TRACEABILITYspec/evidence/release-traceability-readiness.jsonc7327021d39dc67ac5564bc55073b3870a397d79ac8d9648284d56e33bc14a3ePTO-EVIDENCE-INSTRUCTION-CONTRACT-CLOSUREPTO-EVIDENCE-INSTRUCTION-CONTRACT-CLOSUREspec/evidence/instruction-contract-closure.json3ef2bb62421c79dff8fa77a1c7983923b523244b8090812883ef81286ca8106aPTO-EVIDENCE-ARCHITECTURE-READINESSPTO-EVIDENCE-ARCHITECTURE-READINESSspec/evidence/architecture-readiness.json4b0b85199101251bea744e0f3591cc31906909dc80d5ab651c417a936036a004PTO-EVIDENCE-RELEASE-GATE-READINESSPTO-EVIDENCE-RELEASE-GATE-READINESSspec/evidence/release-gate-readiness.jsona0f4d2b6920c08981ea55fd8ef820708a40d4feb5402c5150e8e9ab532d84ce0PTO-EVIDENCE-RELEASE-MANIFESTPTO-EVIDENCE-RELEASE-MANIFESTspec/release-manifest.json1a64c109ed7a90351c41e2a418b3c0ebaf8ad975838986d2101385186b85c0d8{
"classification": [
"data-types",
"memory-operations"
],
"documentation": "docs/arch/data-types/memory-operations.md",
"id": "PTO-ARCH-DATA-TYPES-MEMORY-OPERATIONS",
"mnemonic": null,
"readiness_subjects": [],
"semantic_tests": [],
"source": "asl/arch/data-types/memory-operations.asl",
"surface": "arch",
"tests": [
"PTO-AVS-ARCH-DATA-TYPES-MEMORY-OPERATIONS-STATIC-001"
]
}0.58.5 · Release candidate7dc8b7e5b121d2b2499a2273bebff29e2cd868124c5b08dd7c47caa6b1917185886bd8ea6929a9bf00c2b8578b86ead04e110b71c227eb0ee9843190e32358ee3c8231774c07aa84e332b6178b535d6f6af62d33asl/arch/data-types/memory-operations.asl