( ESNUG 364 Item 7 ) --------------------------------------------- [02/01/01]
Subject: Is report_qor An Undocumented Synopsys DC Or PhysOpt Tcl Command?
> Does anyone know about the report_qor command in dc_shell-t? We use it,
> but I can't find any documentation on it anywhere. Makes me wonder how
> many secret, undocumented features exist in Design Compiler...
>
> ...
> report_qor > ${REPSPATH}/\${TOP_DESIGN}_hier.pass\${PASS}.qor.rpt;
> ...
>
> Is all I found in Solvnet where report_qor was being used in a script for
> budgeting.
>
> - Christian Cabal
> Hewlett Packard
From: jmcalvez@club-internet.fr (Jean-Marc Calvez)
As I understand it, it is an "official" command in psyn_shell (so you want
to look it up there), which is unofficially available in dc_shell/TCL. It
prints out various metrics related to quality of results (number of
violations/TNS/WNS per clock domain, area, synthesis runtime)...
- Jean-Marc Calvez Grenoble, France
---- ---- ---- ---- ---- ---- ----
From: Christian Cabal <cabal@rsn.hp.com>
Thanks.... is psyn_shell the Physical Compiler product? When we use it in
dc_shell-t after a job, it reports this:
Compile CPU Statistics
-----------------------------------
Resource Sharing: 0.00
Logic Optimization: 0.00
Mapping Optimization: 0.00
-----------------------------------
Overall Compile Time: 0.00
is this a bug?
- Christian Cabal
Hewlett Packard
---- ---- ---- ---- ---- ---- ----
From: jmcalvez@club-internet.fr (Jean-Marc Calvez)
Yes, psyn_shell is the Physical Compiler product.
If, by a job, you mean a synthesis run, then it is obviously wrong (or you
have a CPU I would love to get my hands on!). On the other hand, as long as
it remains an undocumented command, you have little ground to complain to
your Synopsys FAE (btw, I got non-zero values in psyn_shell; never tried it
in DC).
- Jean-Marc Calvez Grenoble, France
|
|
