declare simd Directive

The function or subroutine body must be a structured block.

The execution of the function or subroutine, when called from a SIMD loop, cannot result in the execution of an OpenMP construct except for an ordered construct with the simd clause or an atomic construct.

The execution of the function or subroutine cannot have any side eﬀects that would alter its execution for concurrent iterations of a SIMD chunk.

∙ If the function has any declarations, then the declare simd directive for any declaration that has one must be equivalent to the one speciﬁed for the deﬁnition. ∙ The function cannot contain calls to the longjmp or setjmp functions.

∙ The function cannot contain throw statements.

∙ proc-name must not be a generic name, procedure pointer, or entry name. ∙ If proc-name is omitted, the declare simd directive must appear in the speciﬁcation part of a subroutine subprogram or a function subprogram for which creation of the SIMD versions is enabled. ∙ Any declare simd directive must appear in the speciﬁcation part of a subroutine subprogram, function subprogram, or interface body to which it applies. ∙ If a declare simd directive is speciﬁed in an interface block for a procedure, it must match a declare simd directive in the deﬁnition of the procedure. ∙ If a procedure is declared via a procedure declaration statement, the procedure proc-name should appear in the same speciﬁcation. ∙ If a declare simd directive is speciﬁed for a procedure name with explicit interface and a declare simd directive is also speciﬁed for the deﬁnition of the procedure then the two declare simd directives must match. ∙ Procedure pointers may not be used to access versions created by the declare simd directive.


Name: declare simd	Association: declaration
Category: declarative	Properties: pure


Name	Type	Properties

proc-name	identiﬁer of function type	optional

7.7 declare simd Directive