is_arith predicate
CodeArtifactThe `is_arith` predicate is used as a HOL-TestGen test-purpose constraint for selecting arithmetic microprocessor instructions in a VAMP-related test-program generation case study.
First seen 5/26/2026
Last seen 5/26/2026
Evidence 1 chunks
Wiki v1
WIKI
is_arith predicate
is_arith is presented as a test-purpose predicate for arithmetic-instruction testing in the microprocessor test-program generation case study. In the unit-test scenario, it constrains the instruction under test so that generated tests cover arithmetic operations rather than other instruction classes. [C1]
Unit-test usage
NEIGHBORHOOD
No graph connections found for this entity yet. It may appear in future ingestion runs.
explore full graph →RELATIONSHIPS
1 connectionsis_arith is used as a test purpose to constrain test generation to arithmetic operations.
CITATIONS
6 sources6 citations — click to expand
[1] The `is_arith` predicate is used as a test-purpose constraint limiting generated tests to arithmetic operations. Test Program Generation for a Microprocessor: A Case Study
[2] The unit-test setup for arithmetic operations uses `test_spec`, `exec_instr`, `is_arith i`, `gen_test_cases 0 1 SUT`, and stores the result as `arith_instr`. Test Program Generation for a Microprocessor: A Case Study
[3] After generation, each arithmetic operation is covered by one generated test case, with `Iaddi` shown as an example for addition. Test Program Generation for a Microprocessor: A Case Study
[4] The sequence scenario uses `list_all is_arith` over an instruction list and checks execution through `mbind ... execVAMP` with `assertSE`. Test Program Generation for a Microprocessor: A Case Study
[5] A generated arithmetic instruction sequence includes `Isub 2 1 0`, `Iadd 1 5 2`, and `Iadd 1 0 4`, with the assembly excerpt showing `ISUB 2 1 0`. Test Program Generation for a Microprocessor: A Case Study
[6] The paper characterizes arithmetic-test granularity as coarse because registers were modeled as integers rather than `32 word` bitvectors and because HOL-TestGen selects one candidate per variable; it suggests adding case distinctions in test-purpose definitions as a workaround. Test Program Generation for a Microprocessor: A Case Study