User guide

11-10
Race Detection
The following is an example of the command line:
PostRace.pl -minmax 80 250 -f mydesign.race.out -o
mydesign.race.out.post
In this example the output file is named mydesign.race.out.post and
reports on the race conditions between 80 and 250 time units. The
post-process file is named mydesign.race.out.
Modifying the PostRace.pl Script
The first line of the PostRace.pl Perl script is as follows:
#! /usr/local/bin/perl
If Perl is installed at a different location at your site you need to modify
the first line of this script. This script needs a perl5 interpreter. You
will find this script at: vcs_install_dir/bin/PostRace.pl
Debugging Simulation Mismatches
A design can contain several race conditions where many of them
behave the same in different simulations so they are not the cause
of a simulation mismatch. For a simulation mismatch you want to find
the “critical races,” the race conditions that cause the simulation
mismatch. This section describes how to do this.
Add system tasks to generate VCD files to the source code of the
simulations that mismatch. Recompile them with the +race or
+racecd options and run the simulations again.