Dmitry and SV-AC,
The SV-BC discussed this issue during its September 12 meeting.
The SV-BC suggests either accepting the consequences of the change or defining a new feature, e.g. local clocking, as well as the
interaction between the legacy and new features.
SV-BC members have now been notified of the proposed change and can alert others as they feel is needed.
If the SV-AC feels there is a need to get official feedback from member companies, The SV-BC suggests raising this with 1800 WG.
Matt
-- Matt Maidment mmaidmen@ichips.intel.com From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org] On Behalf Of Korchemny, Dmitry Sent: Tuesday, September 06, 2011 3:47 AM To: 'sv-bc (sv-bc@eda.org)'; 'sv-cc@eda-stds.org'; 'sv-ec@eda.org' Cc: Karen Pieper; 'neil.korpusik@oracle.com' Subject: [sv-cc] Mantis 3069: Relax rules for $global_clock resolution (reminder) Hi SV-BC, SV-CC, and SV-EC, Stu requested to review the backward compatibility introduced by Mantis 3069 "Relax rules for $global_clock resolution" (http://www.eda-stds.org/mantis/file_download.php?file_id=5338&type=bug) by your committees: Stu - The proposed changes are not backward compatible with the 2009 standard. The proposal includes a note to this affect, but I am concerned that other committees, vendors and users have not been given an opportunity to consider the implications of this incompatibility. How much existing code will this proposal break, and at how many companies? How difficult will it be for EDA vendors to manage this incompatibility? Is there another way to solve what this proposal is trying to accomplish without breaking backward compatibility? I would prefer any concerns about backward compatibility be addressed by vendors and users before this standard goes to ballot. Please, review. Thanks, 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<http://www.mailscanner.info/>, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Sep 12 11:12:59 2011
This archive was generated by hypermail 2.1.8 : Mon Sep 12 2011 - 11:13:06 PDT