Example

Consider the following pipeline:   Forwarding event In this event, the user wants to test a 'forward' in the pipeline-a situation where data is taken from one execution pipeline stage to another (see the dashed line).   A specific event description This event includes two instructions, with Instruction I2 depending on instruction I1-the source of instruction I2 is the same as the target of instruction I1, and I2 comes after I1 in program order. The timing of the instructions should guarantee that they will be in the requested stage of their execution (see the gray boxes).   A set of events (a coverage model) Here the user wants to validate that every forwarding of all source and target pipeline stages is tested. Piparazzi generates all these events by iteratively generating an event according to the above event description. Piparazzi generates a different random test file for each scenario.