[sv-ac] RE: SV-AC meeting reminder

Hi Dmitry,

I have received this message about 6 times, is there something wrong with your or our mailer?

Thanks,
ed

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of Korchemny, Dmitry
Sent: Tuesday, July 20, 2010 2:02 AM
To: sv-ac@eda.org
Subject: [sv-ac] SV-AC meeting reminder

Date: 2010-07-20
Time: 16:00 UTC (9:00 PDT)
Duration: 1.5 hours

Dial-in information:
--------------------
Meeting ID: 38198

Phone Number(s):
1-888-813-5316 Toll Free within North America
Local dial-in numbers
Australia, St Leonards +61.0.2862.26850
Armenia, Yerevan +374.10.492609
Canada, Mississauga +905.273.8402
Canada, Nepean +613.221.8603
Switzerland, Zurich +41.44.567.1551
Chile, Santiago +56.2.714.6898
China, Beijing +86.105.986.0609
China, Shanghai +86.212.307.2214
China, Shenzhen +8675582519810
Germany, Aachen +49.240.756.3610
Germany, Munich +49.899.932.0192
Denmark, Copenhagen +49.899.932.0192
Finland, Espoo +358 2075 78023
Finland, Tampere +358 2075 78085
France, Montbonnot +33.4.56.38.48.09
France, Montpellier +33.4.56.38.48.09
France, Rungis +33.1.45.12.06.12
France, Sophia +33.4.97.23.97.06
United Kingdom, Livingston +44.15064.86027
United Kingdom, Reading +44.1189.651119
Sweden, Stockholm +49.899.932.0192
Hungary, Budapest +49.899.932.0192
Ireland, Dublin +353.1.4368831
Israel, Herzelia +972.9.9719650
India, Bangalore +91.80.401.88823
India, Hyderabad +91.40.40.331016
India, Nodia +91.80.401.88823
Italy, Agrate Brianza +39.039.6846712
Portugal, Porto +351.2204.15998
Portugal, Lisbon +351.2104.40398
Taiwan, Taipei +886.2.3725.5705
Taiwan, Hsinchu +886.3.558.1800
Japan, Tokyo +81.3.5746.1339
Japan, Osaka +81.3.5746.1339
Singapore, Singapore +65.6393.7140
South Korea, Seoul +82.2.3404.2701

Agenda:
-------

- Reminder of IEEE patent policy.
See: http://standards.ieee.org/board/pat/pat-slideset.ppt

- Minutes approval

- Email ballot results
2557: Rules for passing automatic variables to sequence subroutines are not clear
2722: Errors in Figures 16-14, 16-15, and 16-16
2839: Contradictory statement of increment/decrement operators usage

- New issues
3145: Need to clearly define "maximal property"
3147: Rule c) in 16.17 conflicts with the relaxed rules on clocking of assertions with inferred leading clocking event.
3156: Conflict in description of clocking event of clocking block behavior (SV-EC)

- Issue resolution/discussion
2732: Clarify timing diagram in Figure 16-4. Future value change
2398: Surprising (to some users) interaction between deferred assertions & short-circuiting
2491: Conflicting rules in 16.17 (D7)
1756: The LRM does not indicate how the control tasks $asserton/off/kill affect verification statements in initial blocks
1763: The LRM does not define whether assertion control tasks affect sequence methods and events
1853: BNF for calls to $rose and other sample value system functions.
2485: terminology related to immediate and deferred assertions.
2558: Restriction inside checker construct
2452: No vacuity information about synchronous aborts
2904: Clarify when disable iff condition must occur relative to starting and ending of an attempt
3134: sequence and property range parameters are erroneously defined
3135: Verbal explanation of nexttime and always is misleading for multiple clocks
2871: Clause 16 does not forbid assertion local variables within clocking event expressions
2353: 'classes' missing from description

- Enhancement progress update
2412: Allow clock inference in sequences
2093: Checker construct (Mantis 1900) should permit output arguments

- Opens

---------------------------------------------------------------------

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.