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
SystemRDL 2.0's constraints is the last major feature that is currently unimplemented. Currently, any RDL that contains a constraint block will fail to compile.
An elaborated constraint is exposed to the user as an abstract syntax tree (AST)
Since most users will simply want to dump the constraint to SystemVerilog, provide a built-in framework to do so.
Will require a mechanism for user-defined reference resolution.
Provide some level of constraint validation.
The text was updated successfully, but these errors were encountered:
Is this feature implemented now? With the current version, if the rdl has constraints, the compiler doesn't show any error. But PeakRDL doesn't reflect it in uvm regmodel. Is this PeakRDL issue of SystemRDL Compiler issue?
While SystemRDL-compiler is the parser, PeakRDL is a code generator using SystemRDL-compiler as a library (Python module). In this case I would say, the PeakRDL regmodel tool does not have the code to generate constraints. Also based on this thread, even if the compiler does not crash, it does not seem constraints are properly processed by the parser. In short the feature is not implemented yet.
SystemRDL 2.0's constraints is the last major feature that is currently unimplemented. Currently, any RDL that contains a constraint block will fail to compile.
The text was updated successfully, but these errors were encountered: