请教一个vcs后仿的反标问题

所有的cell delay都是0. 好像都没有用sdf文件里面，就全用的是lib里的值
读sdf文件的时候没有error只有warning.比如io path没有发现。但是cell相关的warning却一个没有。
请问这种情况是怎么回事?
lib的timescale也检查过了，没有问题。真是奇怪。
我的sdf的top是aaa.但我bench里例化了两个aaa.这种情况的话sdf要怎么加载?
谢谢

你写的太简单了，至少把错误代码贴出来吧?

指定一下反标的范围
比如：top.U_aaa1；top.U_aaa2

实例化两个的时候需要分别反标
aaa_1 aaa(...); aaa_2 aaa(...);
反标是:
$sdf_annotate (“xxx.sdf”, aaa_1)；
$sdf_annotate (“xxx.sdf”, aaa_2)；

sdf_annotate函数用错了吧。没有指定对scope

Separate Annotations
----------------------
This example shows separate annotations to distinct portions of a design hierarchy. There is
no configuration file specification, so the SDF Annotator uses the defaults.
module top;
•••
cpu m1(i1,i2,i3,o1,o2,o3);
fpu m2 (i4,o1,o3,i2,o4,o5,o6);
dma m3(o1,o4,i5,i6,i2);
// perform annotation
initial
begin
$sdf_annotate("cpu.sdf",m1,,"cpu.log");
$sdf_annotate("fpu.sdf",m2,,"fpu.log");
$sdf_annotate("dma.sdf",m3,,"dma.log");
end
// stimulus and response-checking
•••
endmodule
Annotation with Arrays of Instances
------------------------------------
This example shows arrays of instance in a design hierarchy. There is no configuration file
specification, so the SDF Annotator uses the defaults.
module top;
•••
cpu ar[1](i1,i2,i3,o1,o2,o3);
fpu ar[2](i4,o1,o3,i2,o4,o5,o6);
dma ar[3](o1,o4,i5,i6,i2);
// perform annotation
initial
begin
$sdf_annotate("cpu.sdf",ar[1],,"cpu.log");
$sdf_annotate("fpu.sdf",ar[2],,"fpu.log");
$sdf_annotate("dma.sdf",ar[3],,"dma.log");
end
// stimulus and response-checking
•••
endmodule
-------------------------------------
$sdf_annotate System Task Syntax
-------------------------------------
$sdf_annotate ( “sdf_file”
{, module_instance}
{, “config_file”}
{, “log_file”}
{, “mtm_spec”}
{, “scale_factors”}
{, “scale_type”} );
Note: You must specify the arguments to the $sdf_annotate system task in the order
shown in the syntax. You can skip an argument specification, but the number of comma
separators must maintain the argument sequence. For example, to specify only the first and
last arguments, use the following syntax:

$sdf_annotate ( “sdf_file”,,,,,, “scale_type”);

Separate Annotations
----------------------
This example shows separate annotations to distinct portions of a design hierarchy. There is
no configuration file specification, so the SDF Annotator uses the defaults.
module top;
•••
cpu m1(i1,i2,i3,o1,o2,o3);
fpu m2 (i4,o1,o3,i2,o4,o5,o6);
dma m3(o1,o4,i5,i6,i2);
// perform annotation
initial
begin
$sdf_annotate("cpu.sdf",m1,,"cpu.log");
$sdf_annotate("fpu.sdf",m2,,"fpu.log");
$sdf_annotate("dma.sdf",m3,,"dma.log");
end
// stimulus and response-checking
•••
endmodule
Annotation with Arrays of Instances
------------------------------------
This example shows arrays of instance in a design hierarchy. There is no configuration file
specification, so the SDF Annotator uses the defaults.
module top;
•••
cpu ar[1](i1,i2,i3,o1,o2,o3);
fpu ar[2](i4,o1,o3,i2,o4,o5,o6);
dma ar[3](o1,o4,i5,i6,i2);
// perform annotation
initial
begin
$sdf_annotate("cpu.sdf",ar[1],,"cpu.log");
$sdf_annotate("fpu.sdf",ar[2],,"fpu.log");
$sdf_annotate("dma.sdf",ar[3],,"dma.log");
end
// stimulus and response-checking
•••
endmodule
-------------------------------------
$sdf_annotate System Task Syntax
-------------------------------------
$sdf_annotate ( “sdf_file”
{, module_instance}
{, “config_file”}
{, “log_file”}
{, “mtm_spec”}
{, “scale_factors”}
{, “scale_type”} );
Note: You must specify the arguments to the $sdf_annotate system task in the order
shown in the syntax. You can skip an argument specification, but the number of comma
separators must maintain the argument sequence. For example, to specify only the first and
last arguments, use the following syntax:
$sdf_annotate ( “sdf_file”,,,,,, “scale_type”);