If the construct is contained in a member function, whether accesses anywhere in the region through the implicit this pointer refer to the new list item or the original list item is unspecified.

A new list item of the same type, with automatic storage duration, is allocated for the construct. The storage and thus lifetime of these list items last until the block in which they are created exits. The size and alignment of the new list item are determined by the type of the variable. This allocation occurs once for each task generated by the construct and once for each SIMD lane used by the construct.

The new list item is initialized, or has an undefined initial value, as if it had been locally declared without an initializer.

If the type of a list item is a reference to a type T then the type will be considered to be T for all purposes of the clause.

The order in which any default constructors for different private variables of class type are called is unspecified. The order in which any destructors for different private variables of class type are called is unspecified.

If any statement of the construct references a list item, a new list item of the same type and type parameters is allocated. This allocation occurs once for each task generated by the construct and once for each SIMD lane used by the construct. If the type of the list item has default initialization, the new list item has default initialization. Otherwise, the initial value of the new list item is undefined. The initial status of a private pointer is undefined.

For a list item or the subobject of a list item with the ALLOCATABLE attribute:

• If the allocation status is unallocated, the new list item or the subobject of the new list item will have an initial allocation status of unallocated;
• If the allocation status is allocated, the new list item or the subobject of the new list item will have an initial allocation status of allocated; and
• If the new list item or the subobject of the new list item is an array, its bounds will be the same as those of the original list item or the subobject of the original list item.

A privatized list item may be storage-associated with other variables when the data-sharing attribute clause is encountered. Storage association may exist because of base language constructs such as EQUIVALENCE or COMMON. If A is a variable that is privatized by a construct and B is a variable that is storage-associated with A then:

• The contents, allocation, and association status of B are undefined on entry to the region;
• Any definition of A, or of its allocation or association status, causes the contents, allocation, and association status of B to become undefined; and
• Any definition of B, or of its allocation or association status, causes the contents, allocation, and association status of A to become undefined.

A privatized list item may be a selector of an ASSOCIATE or SELECT TYPE construct. If the construct association is established prior to a parallel region, the association between the associate name and the original list item will be retained in the region.

Finalization of a list item of a finalizable type or subobjects of a list item of a finalizable type occurs at the end of the region. The order in which any final subroutines for different variables of a finalizable type are called is unspecified.

• A variable of class type (or array thereof) that is privatized requires an accessible, unambiguous default constructor for the class type.

• A variable that is privatized must not have a const-qualified type unless it is of class type with a mutable member. This restriction does not apply to the firstprivate clause.
• A variable that is privatized must not have an incomplete type or be a reference to an incomplete type.

• Variables that appear in namelist statements, in variable format expressions, and in expressions for statement function definitions, must not be privatized.
• Pointers with the INTENT(IN) attribute must not be privatized. This restriction does not apply to the firstprivate clause.
• A private variable must not be coindexed or appear as an actual argument to a procedure where the corresponding dummy argument is a coarray.
• Assumed-size arrays must not be privatized in a target, teams, or distribute construct.