Hi all, I would like to make the following observation, though it is probably too late. Currently the clock inference rules for initial procedures are the same as for always procedures, e.g., in the following case initial @(posedge clk) assert property (a); the clock is inferred, while in initial @clk assert property (a); the clock is not inferred. But essentially these rules were introduced only for consistency reasons, and it would be more natural to infer all events from the sensitivity list of the initial procedure, since synthesis considerations are not valid here. If we change the inference rules in the initial procedure, initial_check will be redundant, and this would simplify everything, including the VPI changes. Though this new definition would break the backward compatibility, I think it will not have any real negative impact. What do you think? Dmitry --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Mar 3 00:39:56 2008
This archive was generated by hypermail 2.1.8 : Mon Mar 03 2008 - 00:40:55 PST