PGI User's Guide

More documents

Recommendations

Info

$Intel(R) Math Kernel Library for Linux* OS User's Guide$

Portability of Multi-Threaded Programs on LinuxTiming functions available with the PGI compilers include these:• 3F timing routines• The SECNDS pre-declared function in PGF77, PGF95, or PGFORTRAN• The SYSTEM_CLOCK or CPU_CLOCK intrinsics in PGF95 or PGHPF.In general, when timing a program, you should try to eliminate or reduce the amount of system level activitiessuch as I/O, program loading, and task switching.The following example shows a fragment that indicates how to use SYSTEM_CLOCK effectively within an F90,F95 or HPF program unit.Example 3.4. Using SYSTEM_CLOCK code fragment. . .integer :: nprocs, hz, clock0, clock1real :: timeinteger, allocatable :: t(:)!hpf$ distribute t(cyclic)#if defined (HPF)allocate (t(number_of_processors()))#elif defined (_OPENMP)allocate (t(OMP_GET_NUM_THREADS()))#elseallocate (t(1))#endifcall system_clock (count_rate=hz)!call system_clock(count=clock0)< do work>call system_clock(count=clock1)!t = (clock1 - clock0)time = real (sum(t)) / (real(hz) * size(t)). . .Portability of Multi-Threaded Programs on LinuxPGI has created two libraries - libpgbind and libnuma - to handle the variations between variousimplementations of Linux.Some older versions of Linux are lacking certain features that support multi-processor and multi-core systems,in particular, the system call 'sched_setaffinity' and the numa library libnuma. The PGI run-time library usesthese features to implement some –Mconcur and –mp operations.These variations have led to the creation of two PGI libraries, libpgbind and libnuma. These libraries are usedon all 32-bit and 64-bit Linux systems, but are not needed on Windows or Mac OS X.When a program is linked with the system libnuma library, the program depends on the libnuma library inorder to run. On systems without a system libnuma library, the PGI version of libnuma provides the requiredstubs so that the program links and executes properly.46
Chapter 3. Optimizing & ParallelizinglibpgbindlibnumaIf the program is linked with libpgbind and libnuma, the differences between systems is masked by thedifferent versions of libpgbind and libnuma. In particular, PGI provides two versions of libpgbind: one forsystems with working support for sched_setaffinity and another for systems that do not.When a program is deployed to the target system, the proper set of libraries, real or stub, should be deployedwith the program.This facility requires that the program be dynamically linked with libpgbind and libnuma.On some versions of Linux, the system call sched_setaffinity does not exist or does not work. The librarylibpgbind is used to work around this problem.During installation, a small test program is compiled, linked, and executed. If the test program compiles, links,and executes successfully, the installed version of libpgbind calls the system sched_setaffinity, otherwise thestub version is installed.Not all systems have libnuma. Typically, only numa systems will have this library. PGI supplies a stub version oflibnuma which satisfies the calls from the PGI run-time to libnuma. Note that libnuma is a shared library that islinked dynamically at run-time.The reason to have a numa library on all systems is to allow multi-threaded programs, such as programscompiled with –Mconcur or –mp , to be compiled, linked, and executed without regard to whether the hostor target systems has a numa library. When the numa library is not available, a multi-threaded program stillruns because the calls to the numa library are satisfied by the PGI stub library.During installation, the installation procedure checks for the existence of a real libnuma among the systemlibraries. If the real library is not found, the PGI stub version is substituted.47
Page 2 and 3:
While every precaution has been tak
Page 5 and 6:
PGI ® Compiler User’s Guide4. Us
Page 7 and 8:
PGI ® Compiler User’s GuideRefer
Page 12 and 13:
xii14.6. Intrinsic Header File Orga
Page 14 and 15:
xiv13.3. Large Array and Small Memo
Page 16 and 17: Organizationxvi• Fortran 95 Handb
Page 18 and 19: Conventionsin this guide with which
Page 21 and 22: Chapter 1. Getting StartedThis chap
Page 23 and 24: Chapter 1. Getting StartedWhere:opt
Page 25 and 26: Chapter 1. Getting Startedfilename.
Page 27 and 28: Chapter 1. Getting Startedfilename.
Page 29 and 30: Chapter 1. Getting Startedparallel
Page 31 and 32: Chapter 1. Getting Startedas execut
Page 33 and 34: Chapter 1. Getting Startedar or ran
Page 35 and 36: Chapter 1. Getting StartedTo do thi
Page 37 and 38: Chapter 2. Using Command LineOption
Page 39 and 40: Chapter 2. Using Command Line Optio
Page 41 and 42: Chapter 2. Using Command Line Optio
Page 43 and 44: Chapter 3. Optimizing & Parallelizi
Page 65: Chapter 3. Optimizing & Parallelizi
Page 70 and 71: Invoking Function Inlining50except:
Page 72 and 73: Creating an Inline Librarylevel of
Page 74 and 75: Restrictions on InliningA Fortran s
Page 76 and 77: OpenMP OverviewFortran directives a
Page 78 and 79: Task OverviewN = 1000DO I = 1, NV(I
Page 80 and 81: C/C++ Parallelization PragmasC/C++
Page 82 and 83: Directive and Pragma ClausesFortran
Page 84 and 85: Directive and Pragma ClausesThis cl
Page 86 and 87: Run-time Library RoutinesRun-time L
Page 88 and 89: Run-time Library RoutinesRun-time L
Page 90 and 91: Environment VariablesRun-time Libra
Page 93 and 94: Chapter 6. Using MPIMessage Passing
Page 95 and 96: Chapter 6. Using MPIyou are using M
Page 97 and 98: Chapter 6. Using MPIthe root of the
Page 99 and 100: Chapter 6. Using MPIcorrelated with
Page 101: Chapter 6. Using MPI• Add the fol
Page 104 and 105: TerminologyAvailability84The PGI 11
Page 106 and 107: System Requirements86Vector operati
Page 108 and 109: Memory Model88• waits for complet
Page 110 and 111: Accelerator DirectivesAccelerator D
Page 112 and 113: Accelerator Directives• Initial d
Page 114 and 115: Accelerator DirectivesThis directiv
Page 116 and 117:
Accelerator Directive ClausesUse th
Page 118 and 119:
Environment Variables• Interfaces
Page 120 and 121:
PGI Unified Binary for Accelerators
Page 122 and 123:
Profiling Accelerator KernelsWith '
Page 124 and 125:
Supported IntrinsicsTable 7.5. Supp
Page 126 and 127:
References related to AcceleratorsT
Page 128 and 129:
PGI Proprietary C and C++ Pragmas10
Page 130 and 131:
Scope of Fortran Directives and Com
Page 132 and 133:
Scope of C/C++ Pragmas and Command-
Page 134 and 135:
Prefetch Directives and Pragmas114d
Page 136 and 137:
C$PRAGMA CTable 8.2. !DEC$ Directiv
Page 138 and 139:
Using System Library Routines118voi
Page 140 and 141:
Creating and Using Dynamic Librarie
Page 142 and 143:
Creating and Using Dynamic-Link Lib
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Using LIB3FStep 3: Run the exe to e
Page 152 and 153:
Setting Environment VariablesIn bas
Page 154 and 155:
PGI-Related Environment VariablesEn
Page 156 and 157:
PGI Environment VariablesLD_LIBRARY
Page 158 and 159:
PGI Environment VariablesNCPUS138Se
Page 160 and 161:
PGI Environment VariablesThe value
Page 162 and 163:
Using Environment Modules on LinuxT
Page 164 and 165:
144
Page 166 and 167:
Deploying Applications on Linux146T
Page 168 and 169:
Code Generation and Processor Archi
Page 170 and 171:
150
Page 172 and 173:
Inter-language Calling Consideratio
Page 174 and 175:
Compatible Data TypesNoteFortran Ty
Page 176 and 177:
Array Indices! Fortran function ret
Page 178 and 179:
ExamplesCompile and execute the pro
Page 180 and 181:
Examples160int a,b,c;a=8; b=2;print
Page 182 and 183:
Win32 Calling Conventionscout
Page 184 and 185:
Win32 Calling Conventions164call wo
Page 186 and 187:
166
Page 188 and 189:
Large Static Data in LinuxC/C++ Dat
Page 190 and 191:
Practical Limitations of Large Arra
Page 192 and 193:
Medium Memory Model and Large Array
Page 194 and 195:
Large Array and Small Memory Model
Page 196 and 197:
Extended Inline AssemblyExtended In
Page 198 and 199:
Extended Inline Assemblyexample2:..
Page 200 and 201:
Extended Inline Assembly180movq %rs
Page 202 and 203:
Extended Inline AssemblyConstraintw
Page 204 and 205:
Extended Inline AssemblyConstraintu
Page 206 and 207:
Extended Inline AssemblyConstraintM
Page 208 and 209:
Extended Inline AssemblyModifierDes
Page 210 and 211:
Intrinsicsvoid example21(){void * s
Page 212 and 213:
suboptions, 18syntax, 2, 17Commands
Page 214 and 215:
InstallLinux portability package, 1
Page 216 and 217:
modifier *, 186, 186modifier &, 186
Page 218:
optimization, 39-tp option, 39UNIXc
show all

PGI User's Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?