Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
language:langs:spec [2023/11/18 11:56]
rajit [Timing constraints]
language:langs:spec [2024/12/19 07:18] (current)
rajit [Exclusive directives]
Line 20: Line 20:
  }  }
 </code> </code>
-states that the signals ''a'' and ''b'' will not be true (high) simultaneously, and this is guaranteed by the production rules in the circuit.+states that the signals ''a'' and ''b'' will not be true (high) simultaneously, and this is guaranteed by the production rules in the circuit. Violations of this requirement can be detected by ''actsim'' when it is run with the ''-m'' option.
  
 To simplify modeling of arbiters that cannot be modeled purely at the digital level of abstraction, we include a specific directive that we call "make exclusive high". To simplify modeling of arbiters that cannot be modeled purely at the digital level of abstraction, we include a specific directive that we call "make exclusive high".
Line 53: Line 53:
 === Timing constraints === === Timing constraints ===
  
-Timing constraints in ACT are specified using timing forks. Timing forks are used to specify a point of divergence relative timing constraint. The constraint +Timing constraints in ACT are specified using [[asic:timing:forks|timing forks]]. Timing forks are used to specify a point of divergence relative timing constraint. The constraint 
 <code act> <code act>
 spec { spec {