Subject: Re: [sv-ac] R29a/b Optional or mandatory name for assertions/properties/assumptions.
From: David Lacey (dlacey@rsn.hp.com)
Date: Thu Sep 19 2002 - 07:04:26 PDT
The problem with using line numbers, however, is it makes it diffucult
to merge coverage data across mutliple model releases. Since the line
an assertion is on may change as the model is modified, each model's
coverage data will have different names for the monitors.
David
John Havlicek wrote:
>
> > Who envisions a tool [theirs or another] that uses names and will
> > make them optional?
>
> Our internal tools already do this. We collect code coverage on the
> specifications themselves. We do not ask the user to provide a name
> for every specification line on which coverage is collected, but we
> do provide the user the option to label lines, in which case the
> user label replaces the automatically generated name (file, line number).
> The coverage reports are annotated with information about the nature
> of the line so that the automatically generated name is more meaningful
> when scanning the report.
>
> Best regards,
>
> J.H.
-- David J. Lacey Design Verification Hardware Scientist Email: dlacey@rsn.hp.com Phone: 972-497-4114
This archive was generated by hypermail 2b28 : Thu Sep 19 2002 - 07:05:32 PDT