Subject: Re: 1364.1 pragmas
From: Shalom Bresticker (Shalom.Bresticker@motorola.com)
Date: Thu Aug 29 2002 - 01:52:31 PDT
So it is just the same as in comments.
In comments, too, tools detect whether the comment is a directive for them
by looking at the beginning.
I do have a reservation about the synthesis "keyword" in that it seems to
reserve the following attributes just for synthesis tools.
One of the problems today is that each tool has its own directives
and we find that we want tools to be able to read directives intended for other
tools.
We want formal verification tools to read fullcase directives, also, for
instance.
I would not want to have to repeat myself:
(* synthesis, fullcase *)
(* fv, fullcase *)
So why restrict them by a misleading domain name which implies that they
are used only by tools in that domain?
Shalom
Paul Graham wrote:
> > The nice thing about (* synthesis, <other attributes> *) is that
> > "synthesis" now does become a domain keyword and the 1364.1 Standard
> > requires that it be listed first, which helps synthesis tools to quickly
> > identify and read only attributes that are intended for that tool.
>
> Why is it necessary to give a synthesis tool additional aid in quickly
> identifying and reading synthesis attributes? Right now a synthesis tool
> must scan every comment in the input rtl to check for pragmas. Replacing
> comment pragmas by attributes will reduce the search from typically hundreds
> or thousands of comments per design to probably tens of attributes. Even
> so, comment parsing is such an infinitesimally small part of a synthesis
> tool, in terms of lines of code and total run-time, that there's no need to
> try to make it easier on the tool.
>
> Paul
-- Shalom Bresticker Shalom.Bresticker@motorola.com Design & Reuse Methodology Tel: +972 9 9522268 Motorola Semiconductor Israel, Ltd. Fax: +972 9 9522890 POB 2208, Herzlia 46120, ISRAEL Cell: +972 50 441478"The devil is in the details."
This archive was generated by hypermail 2b28 : Thu Aug 29 2002 - 02:03:35 PDT