Hi all, I updated the proposal according to John's comment, and it is ready to vote. JH: - 16.18.6, pp. 16-17. The intuitive descriptions of the assumptions imposed on the free checkvar bit flag seem reasonable for a formal tool in which $global_clock ticks at every point in time. In simulation, however, $global_clock may not be at the granularity of a timestep and a simulator may apply chaotic values for flag in timesteps that are not ticks of $global_clock. In this situation, the intuitive descriptions do not seem accurate. I recommend either 1. Stating that it is assumed that $global_clock ticks at every timestep, or 2. Qualifying the intuitive descriptions in a way that makes it clear that they apply only in the timesteps in which $global_clock ticks. Original text: Simulators may assign arbitrary values to the variable flag. They may use assumptions m1, m2, and m3 to constrain the values generated if they have the capability to do so. New text: Simulators may assign arbitrary values to the variable flag. They may use assumptions m1, m2, and m3 to constrain the values generated at the $global_clock ticks if they have the capability to do so. The new version is checkers_080213dk.pdf, and it addresses the comments from the champions' review and fixes of several other fixes. To ease the review, note the following: * At the beginning of the proposal there is modification history, where the changes are documented. * You can download the original Word version approved by SV-AC, checkers_080121dk.doc and the new Word version, checkers_080213dk.doc. Then open one of these documents, Select Tools --> Compare and merge documents, select the other document, and you will see the changes. 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, and is believed to be clean.Received on Wed Feb 13 01:38:54 2008
This archive was generated by hypermail 2.1.8 : Wed Feb 13 2008 - 01:39:19 PST