execVAMP function

CodeArtifact

The execVAMP function is a lifting of exec_instr into the state-exception monad used in test specifications for generated VAMP instruction sequences. It executes a VAMP instruction against a machine state by returning a successful monadic result containing unit and the state produced by exec_instr.

First seen 5/25/2026

Last seen 5/26/2026

Evidence 3 chunks

Wiki v1

WIKI

Overview

execVAMP is defined in the VAMP microprocessor testing case study as a lifted execution function for VAMP instructions. The paper describes it as “a lifting of exec_instr into the state exception monad” and gives the definition:

definition execVAMP where execVAMP ≡ (λ i σ. Some ((), exec_instr σ i))

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

3 connections

exec_instr function uses → 100% 1e

execVAMP is a lifting of exec_instr into the state exception monad.

state-exception monad uses → 100% 1e

execVAMP lifts exec_instr into the state-exception monad.

Test Program Generation for a Microprocessor: A Case-Study ← uses 100% 1e

The paper uses execVAMP as the system stepping function in test specifications.

LINKED ENTITIES

2 links

state-exception monad USES Extracted graph relationship

VAMP ISA EXECUTES Extracted graph relationship

CITATIONS

8 sources

8 citations — click to expand

[1] execVAMP is defined as a lifting of exec_instr into the state-exception monad. Test Program Generation for a Microprocessor: A Case Study

[2] The formal definition of execVAMP is λ i σ. Some ((), exec_instr σ i). Test Program Generation for a Microprocessor: A Case Study

[3] execVAMP is used with mbind to execute generated instruction sequences in final-state test specifications. Test Program Generation for a Microprocessor: A Case Study

[4] The relevant test scenarios in the case study assert properties over the final state rather than observing local execution steps. Test Program Generation for a Microprocessor: A Case Study

[5] Test specification preconditions are also called test purposes and restrict generated instruction sequences to a selected subset. Test Program Generation for a Microprocessor: A Case Study

[6] The study uses an empty initial configuration σ0 that is proved well formed. Test Program Generation for a Microprocessor: A Case Study

[7] The testing work stays at the design level of the VAMP machine, despite the availability of a VAMP gate-level model. Test Program Generation for a Microprocessor: A Case Study

[8] The is_load_store test purpose restricts the first test scenario to load and store operations by constraints over VAMP assembly syntax. Test Program Generation for a Microprocessor: A Case Study