Section 8.6

In Syntax 8-6 replace join with join | join_any | join_none

In 1^st paragraph change as indicated in blue:

Verilog allows a begin...end,fork...join, fork…join_none, or fork…join_any statement block to be named.

In 2^nd paragraph change as indicated in blue:

SystemVerilog allows a matching block name to be specified after the block end, join, join_none, or join_any keyword, preceded by a colon. This can help document which end, join, join_none, or join_any is associated with which begin or fork when there are nested blocks.

In the 4^th paragraph change as indicated in blue:

A begin...end, fork...join, fork…join_none, or fork…join_any block is considered a statement, and can have a statement label before the block.

In the 5^th paragraph change as indicated in blue:

A label cannot appear before the end, join, join_none, or join_any as these keywords do not form a statement.

In Section 9.7 change the syntax as shown in blue:

fork

statement1;

statement2;

...

statementn;

[join | join_any | join_none]

In Section 9.7 paragraph change as indicated in blue:

The join options of join_any or join_none specify when the parent (forking) process resumes execution.

In Section 9.7 Table 9-1

Replace all with join

Replace any with join_any

Replace none with join_none

In Section 9.7 in the last example replace “join none” with join_none

In Section 9.9.1 replace “join any” with join_any and “join none” with jone_none in the example.

In Section 9.9.2 replace “join any” with join_any in the example.

In Section 9.9.3 replace “join none” with jone_none in the example.

In Section 11.24 replace “join none” with jone_none in the example.

In Section 12.9 replace “join none” with jone_none in the example.

In Annex B remove all, any and none from keyword list. Add join_none and none_any to the keyword list.