[sv-ac] RE: 2091 changes

Hi John,

 

I have made the requested changes. Hopefully we can voice vote on this
next week.

 

    JH: Yes, friendly amendments.

    - p. 2, first bullet, change "shall not be referenced in an
assertion"

      to "shall not be referenced in a concurrent assertion".

    - p. 2, change "All variables in an assertion" to "All variables in 

      a concurrent assertion"

 

 

Also, you had asked another question:  Does the statement "concurrent
assertions shall only exist in blocks whose lifetime is also static"
prevent concurrent assertions in for-loops. I think the answer is no
based on the following:

 

seq_block ::=

begin [ : block_identifier ] { block_item_declaration } {
statement_or_null }

end [ : block_identifier ]

par_block ::=

fork [ : block_identifier ] { block_item_declaration } {
statement_or_null }

join_keyword [ : block_identifier ]

 

statement_item ::=

blocking_assignment ;

| nonblocking_assignment ;

| procedural_continuous_assignment ;

| case_statement

| conditional_statement

| inc_or_dec_expression ;

| subroutine_call_statement

| disable_statement

| event_trigger

| loop_statement

| jump_statement

| par_block

| procedural_timing_control_statement

| seq_block

| wait_statement

| procedural_assertion_statement

| clocking_drive ;

| randsequence_statement

| randcase_statement

| expect_property_statement

 

The content of a block is a statement_or_null, and the statement can be
a loop_statement. So while a for loop itself may or may not be a block,
it will be contained within a block.

 

Lisa

 

-----Original Message-----
From: John Havlicek [mailto:john.havlicek@freescale.com] 
Sent: Thursday, February 14, 2008 2:14 PM
To: Lisa Piper
Subject: 2091 changes

 

22. 2091  SV-AC  Need a clarification where concurrent assertions may
appear

    - Fixed

    - 2008-01-29: Voice vote approved all friendly amendments, 8y/0n/0a.

 

    JH: Yes, friendly amendments.

    - p. 2, first bullet, change "shall not be referenced in an
assertion"

      to "shall not be referenced in a concurrent assertion".

    - p. 2, change "All variables in an assertion" to "All variables in 

      a concurrent assertion"


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.