|
Comparescan User Guide |
|
Getting Started |
|
|
Table 2-1 Comparescan Command-Line Options, continued |
|
|
|
Option |
Description |
|
|
-r 1 |
Print a summary report to the standard output. A summary |
|
report consists of the first 10 errors, sorted by time, that are |
|
listed in the current error database. You must type a space |
|
character between the r and the 1. See “report” on page 91 for |
|
more information on using summary reports. |
-r 2 |
Print a full report to the standard output. A full report consists |
|
of all of the errors in the current error database. You must type a |
|
space character between the r and the 2. See “report” on |
|
page 91 for more information on using full reports. |
-run |
Run a comparison immediately upon startup. |
-save filename |
Save the binary error database into the file called filename |
|
at the end of the comparison. See “savedata” on page 92 for |
|
more information on saving error databases. |
-state filename |
Specify a state filename and location, overriding the default of |
|
~/.comparescan.state. |
-v[ersion] |
Display the Comparescan version number. |
|
|
Specifying Input Files
Comparescan operates on one of the following inputs:
■One simulation results database. (You can compare two objects from the same database.)
■Two simulation results databases.
■A Comparescan database of comparison mismatches.
Specifying Simulation Results Databases for Comparison
There are three ways to specify simulation results databases for comparison:
■Include the database filename on the command line. You must specify the golden file
first. If you use the -batch option described above, you must specify your database files on the command line. See “Generating a Comparescan Error Database” on page 18 for an example that uses comparescan -batch.
December 2000 |
12 |
Product Version 1.9 |
Comparescan User Guide
Getting Started
■Use the datafile1 and datafile2 commands in a rules file. You specify the name of the golden file with the datafile1 command. See ““Specifying a Comparescan Rules File” on page 13” and “Reviewing the demo.rules Rules File” on page 31 for more information and for examples of using the datafile commands.
■Use the Compare Options form. See “Compare Options Form” on page 40 for instructions on how to do this.
You can specify any supported simulator results files. If your database files are not in SST2 database format, then Comparescan converts them for you. For example, if you enter the following command:
% comparescan adder1.trn adder1-fast.dump
Your directory will contain the files adder1-fast.dsn and adder1-fast.trn after you run Comparescan.
See “translate” on page 94 for information on how Comparescan translates a database into SST2 format.
Important
If you specify simulation results files that are not in SST2 database format (.trn files), some information, such as port or connectivity information, may be lost.
Specifying a Comparescan Rules File
There are two ways to specify a Comparescan rules file:
■Include the name of your rules file on the command line. See “Generating a Comparescan Error Database” on page 18 for an example.
■Use the Compare Options form. See “Compare Options Form” on page 40 for instructions on how to do this.
If you do not specify a Comparescan rules file (see Chapter 6, “Writing Comparescan Rules” for instructions on creating rules files), Comparescan uses either the rules file that is specified in the state file, ~/.comparescan.state (from the last time you ran Comparescan) or a built-in default set of rules. (See “Default Comparison Rules” on page 56 for a listing of the default comparison rules.)
If your rules file specifies the two simulation results files that you want to compare, then you only need to specify the rules file on the command line, as follows:
% comparescan completecompare.rules
December 2000 |
13 |
Product Version 1.9 |