Wrapper Class

CodeArtifact

A wrapper class is described as a likely architectural requirement in a multi-class constrained-random instruction generator when the test layer directly controls lower-level subclass variables. In that flow, the wrapper constrains test-controlled variables, is randomized first, and is followed by allocation and randomization of the appropriate subclass object.

First seen 5/24/2026

Last seen 5/25/2026

Evidence 1 chunks

Wiki v1

WIKI

Overview

In the cited multi-class randomization architecture for an instruction generator, a wrapper class is presented as a likely solution for cases where the test layer directly controls items in lower-level subclasses. The architecture otherwise uses knobs or switches at the upper layer to choose an opcode category first, allowing the generator to allocate the correct subclass object before randomization.

Role in multi-class randomization

READ FULL ARTICLE →

NEIGHBORHOOD

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

explore full graph →

CITATIONS

5 sources

5 citations — click to expand

[1] The multi-class architecture split a large opcode class into smaller opcode-category classes to reduce the size of the randomization problem. Generating AMD microcode stimuli using VCS constraint solver

[2] The base instruction class contained common data members, common constraints, and shared methods, while child classes contained opcode-category-specific constraints. Generating AMD microcode stimuli using VCS constraint solver

[3] When upper-layer generation is controlled only by knobs, the opcode category can be selected first so the correct subclass object can be allocated. Generating AMD microcode stimuli using VCS constraint solver

[4] If the test layer directly controls lower-level subclass items, a wrapper class would likely be required to constrain test-controlled variables. Generating AMD microcode stimuli using VCS constraint solver

[5] In the wrapper-class flow, the wrapper is randomized first, after which the correct subclass object is allocated and randomized in a second phase. Generating AMD microcode stimuli using VCS constraint solver