You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should add the ability to specify the value of an attribute using a parameter. The classic example of this is a multiplier with a parameter-defined latency:
This will become useful if/when we want to define memories with parameter-defined read and write latencies and other parameterized pipelined components.
The implementation challenge is exposing this nicely in the IR. Currently, we just query the underlying primitive object and read off it's attribute field. With this change, we'll also need to resolve the parameter value. However, this logic also exists for PortDefs since primitive ports can have parameter-defined bitwidths.
The text was updated successfully, but these errors were encountered:
I think we should add the ability to specify the value of an attribute using a parameter. The classic example of this is a multiplier with a parameter-defined latency:
This will become useful if/when we want to define memories with parameter-defined read and write latencies and other parameterized pipelined components.
The implementation challenge is exposing this nicely in the IR. Currently, we just query the underlying
primitive
object and read off it's attribute field. With this change, we'll also need to resolve the parameter value. However, this logic also exists forPortDef
s since primitive ports can have parameter-defined bitwidths.The text was updated successfully, but these errors were encountered: