PGI Fortran - Servidor WWW del Cluster Ladon-Hidra

subroutine omp_unset_lock(integer_var)causes the calling thread to release ownership of the lock associated with integer_var. It is illegalto make a call to this routine if integer_var has not been associated with a lock.logical function omp_test_lock(integer_var)causes the calling thread to try to gain ownership of the lock associated with integer_var. Thefunction returns .TRUE. if the thread gains ownership of the lock, and .FALSE. otherwise. It isillegal to make a call to this routine if integer_var has not been associated with a lock.8.17 Environment VariablesOMP_NUM_THREADS specifies the number of threads to use during execution of parallel regions.The default value for this variable is 1. For historical reasons, the environment variable NCPUS issupported with the same functionality. In the event that both OMP_NUM_THREADS and NCPUSare defined, the value of OMP_NUM_THREADS takes precedence.Note: OMP_NUM_THREADS threads will be used to execute the programregardless of the number of physical processors available in the system. As aresult, you can run programs using more threads than physical processors and theywill execute correctly. However, performance of programs executed in thismanner can be unpredictable, and oftentimes will be inefficient.OMP_SCHEDULE specifies the type of iteration scheduling to use for DO and PARALLEL DOloops which include the SCHEDULE(RUNTIME) clause. The default value for this variable is“STATIC”. If the optional chunk size is not set, a chunk size of 1 is assumed except in the case ofa STATIC schedule. For a STATIC schedule, the default is as defined in the DO...END DO andPARALLEL...END PARALLEL sections. Examples of the use of OMP_SCHEDULE are asfollows:$ setenv OMP_SCHEDULE “STATIC, 5”$ setenv OMP_SCHEDULE “GUIDED, 8”$ setenv OMP_SCHEDULE “DYNAMIC”OMP_DYNAMIC currently has no effect.OMP_NESTED currently has no effect.OpenMP Directives for Fortran 303