Subject: Attribute "encoding"
From: Jayaram Bhasker (jbhasker@cadence.com)
Date: Tue Jan 22 2002 - 14:04:19 PST
Still working on adding the new attributes to the draft. However, am not yet clear
how the "encoding" attribute works.
The way it is defined currently, it applies to a reg, such as:
(* synthesis, encoding = "onehot" *) reg [3:0] counter;
So what does this mean? Does it mean that counter can only have onehot values?
What if user assigns a value "1100" to it explicitly? What if user says
"counter = counter + 1"? This attribute can further cause
potential mismatches in simulation.
I believe that this attribute applies only to state registers when describing a design using
a VERY SPECIFIC FSM style and therefore does not apply to the standard that we are
currently working on.
- bhasker
--J. Bhasker Cadence Design Systems 7535 Windsor Drive, Suite A200, Allentown, PA 18195 (610) 398-6312, (610) 530-7985(fax), jbhasker@cadence.com
This archive was generated by hypermail 2b28 : Tue Jan 22 2002 - 14:15:36 PST