HP UX Fortran Software manual Format field widths, Floating-point constants, Intrinsic functions

Page 132

Table 38 f77 options replaced by f90 options (continued)

f77 option

f90 replacement

-D

+dlines

+es

+extend_source

-F

+cpp_keep

-L

+list

-onetrip

+onetrip

+Q

+pre_include

+s

a+langlvla

+T

+fp_exception

+ttyunbuf

+nottybuf

-U

+uppercase

-u

+implicit_none

-V

+lista

a Does not fully replace.

Format field widths

HP Fortran 90 supports format field widths up to 32767. In contrast, HP FORTRAN 77 allows format field widths up to 2147483639, which is close to 2**31.

Floating-point constants

The HP Fortran compiler differs from HP FORTRAN 77 in its handling of floating-point constants. The HP Fortran compiler conforms to the standard: a single-precision constant is treated as a single-precision data item in all situations, regardless of how many digits were supplied when specifying it. HP FORTRAN 77 actually scans and saves constants internally in double precision. This behavior can produce slightly different results.

In HP Fortran, the statement

DOUBLE PRECISION x = 3.1415926535

will initialize to only 32 bits worth of the constant because it interprets the constant as single precision. Under HP Fortran, a constant must have a D exponent or aKIND suffix to be interpreted as double precision.

In programs that use double precision exclusively, you should consider using the

+real_constant=doubleoption, which causes real constants to default to double precision. For more information, see “Controlling data storage” (page 67).

Intrinsic functions

The Fortran 90 standard has introduced new intrinsics that may collide with function or subroutine names in FORTRAN 77 code. You can resolve such collisions by declaring all procedures that you have written—but especially those that have the same name as nonstandard HP Fortran intrinsics—with the EXTERNAL statement. For a list of nonstandard HP Fortran intrinsics, see Table 11-4 on page 239.

Also, HP FORTRAN 77 allows intrinsics to accept a wider variety of argument types than HP Fortran does. For example, in HP FORTRAN 77 the MAX andMIN intrinsics can take arguments of different types, while HP Fortran follows the standard and requires all arguments to be of the same type.

132 Migrating to HP Fortran

Image 132
Contents HP Fortran Programmer Guide AbstractPage Contents Using the on statement Controlling data storageDebugging Performance and optimizationUsing Fortran directives 123 Writing HP-UX applications 107Calling C routines from HP Fortran 110 Migrating to HP Fortran 131Fortran 2003 Features 151 Porting to HP Fortran 141Documentation Feedback 153 Glossary 154 Index 159 HP secure development lifecycle An overview of HP Fortran HP Fortran compiler environmentAn overview of HP Fortran Driver Options for controlling the f90 driver+dryrun +preinclude= filePreprocessor Options for controlling the C preprocessorFront-end Options for controlling the front end+moddir=directory Back-end Options for controlling optimizationOptions for controlling code generation +OnooptimizationOptimization +DAmodelLinker Options for controlling the Linker+FPflags LdirectoryOoutfile Tools HP-UX operating systemWl ,options Compiling with the f90 command F90 command syntaxCompiling and linking $ f90 hello.f90Command-line options F90 command syntaxCommand-line options Example 2 hello.f90Command-line options by category Commonly-used optionsCommonly-used options +saveOption descriptions Options listed by categoryExample 3 Example Do I+1, N+allowunaligned Data type sizes and +autodbl4 14164+autodbl +autodbl4 Boption+cpp=default +charlit77+check=bounds +nocfcName=def +DAmodel+DDdatamodel DatamodelareBlended ItaniumItanium2 NativeValues for the +FP option Signals recognized by the +fpexception option Gformat77+hugecommon Example 4 % f90 +hugecommon=results pcvals.f90 /usr/include directory +noimplicitnone +indirectcommonlist=file+initheapcomplex=rvalival +initheapinteger=ival+io77 Ipo+nocheckuf +nolibsLevels of optimization Requires concurrent use of the +Oprofile=use optionWith different values of optlevel +noobjdebug+pa1 +demandload option. The default is +nodemandload +nodemandload the default+r8 +realconstant=singleTx,path Tp,/usr/ccs/lbin/cppF90com End.oWx,arg1,arg2,...,argN Symbol binding options Bdefault=symbol,symbolBextern =symbol ,symbol Bhidden =symbol ,symbolUsing optimization options Reviewing general optimization optionsF90 +O3 +Osize myprog.f90 +Oconservative +Onoall+Onoautopar +Oautopar and omit +OparallelFine-tuning optimization options F90 +O3 +Onomoveflops +Ofltacc myprog.f90Default is +Onocxlimitedrange Default is +Odataprefetch+Ocachepadcommon option +Onocxlimitedrange+Onofenvaccess +Onofastaccess+Onoentrysched +OnofailsafeOptimizations performed by +Onofltacc +Oinlinebudget=n +Oinlinebudget enables +Onoinline+Onoinlinefilename +Onoinline=function1,function2Values for the +Oinlinebudget option Millicode versions of intrinsic functions+inlinelevel num +Onoloopunroll=factor+Oloopunroll=4 +OnoloopunrolljamDefault is+Onoparmsoverlap +Oparallelintrinsics+Onoparmsoverlap +OnopipelineDefault is +Onopromoteindirectcalls +OnorecoveryDefault is +Oshortdata=8 For +Oprofile=collectarc,strideFilenames Filenames recognized by f90Linking HP Fortran programs Linking with f90 vs. ldLibraries linked by default on PA-RISC Libraries linked by default on ItaniumLinking to libraries $ f90 -c hello.f90 # compileLinking to nondefault libraries Linking HP Fortran 90 routinesAdditional HP Fortran libraries Linking to shared librariesOpt/fortran90/lib/pa2064/ -lF90 -lisamstub Special-purpose compilations Compiling programs with modulesLibrary search rules $ f90 -Wl,-a,archive prog.f90 -lmSpecial-purpose compilations Examples ExampleExample 6 Example 2-2 main.f90 Example 7 Example 2-3 code.f90Compiling with make Example 8 Example 2-4 data.f90$ f90 -o dostats data.f90 code.f90 main.f90 $ dostatsCompiling for different PA-RISC machines Managing .mod filesExample 9 Example 2-5 makefile $ makeCreating shared libraries Compiling with +picUsing the C preprocessor Linking with -bUsing the C preprocessor Processing cpp directivesExample 13 Example 2-9 cppdirect.f90 $ f90 +cpp=yes -D Debug cppdirect.f90Creating demand-loadable executables Creating shared executablesSaving the cpp output file Compiling in 64-bit mode Using environment variables$ f90 +noshared prog.f90 HP Fortran environment variablesF90ROOT environment variable STF90COM64 environment variableHPF90OPTS environment variable $ f90 +list hello.f90Floating installation Floating installationLpath environment variable Mpnumberofthreads environment variableSetting up floating installation Alternate-path/opt/fortran90.3.6.1Controlling data storage Disabling implicit typingAutomatic and static variables Disabling implicit typingContains Controlling data storageIncreasing the precision of constants Increasing default data sizes Increasing default data sizesIncreasing default data sizes Sharing data among programs Usr/lib/libpthread.slWhich creates multiple threads $ gotosleep Sharing data among programsModules vs. common blocks $ wakeupIm up Modules vs. common blocks Using the HP WDB debugger DebuggingStripping debugging information Signals recognized by +fpexception SignalHandling runtime exceptions Floating-point exceptionsBus error exception Floating-point exceptions= 1.0/0.0 Illegal instruction exception Segmentation violation exceptionUsing debugging lines Bad argument exceptionUsing the on statement Exceptions handled by the on statementOn REAL8 DIV 0 Call divzerotrap Exceptions handled by the on statementActions specified by on On Double Precision DIV 0 Call divzerotrapExceptions handled by the on statement Ignoring errors Terminating program executionExample 14 Example5-1 abort.f90 Example 15 Example5-2 ignore.f90Calling a trap procedure Trapping floating-point exceptionsTrapping integer overflow exceptions On Double Precision Overflow Call trapTrapping +Ctrl-C trap interrupts Allowing core dumpsExample 17 Example5-4 callitrap.f90 Example 18 Example 5-5 allowcore.f90 On Real Overflow IgnoreUsing profilers Using profilersPerformance and optimization HP CaliperComparing Program Performance Opt/ansic/bin/cc -Aa +O3 -o program +Oprofile=collectProgram.c ProgramprogramargumentsUsing Options to Control Data Collection GprofSpecifying PBO file names and locations $ gprof prog gprof.outUsing options to control optimization Using +O to set optimization levelsProf $ f90 +O4 file.f90Using the optimization options +O2, -O+O3 +O4Fine-tuning optimization options $ f90 +02 +Oaggressive +Osize prog.f90$ f90 +O4 +Oaggressive +Ofltacc prog.f90 Packaged optimization optionsIs +Onofastaccess at +Ofastaccess at level+O2 +Ofltacc=relaxed+Ofltacc=relaxed . This Fast+Onoinitcheck +Oinlinelevel num +Onolibcalls+Olibcalls +Onoloopunroll=n+Onoparminit +Opipeline+Orecovery +Oregreassoc +Onoreturn+Oshortdata=8 +Ovectorize option onConservative vs. aggressive optimization +Onowholeprogrammode+Owholeprogrammode Conservative, aggressive, and default optimizations Parallelizing HP Fortran programsCompiling for parallel execution F90 +O3 +Oparallel -c x.f90 y.f90 F90 +O3 -c z.f90Performance and parallelization Profiling parallelized programsConditions inhibiting loop parallelization Calling routines with side effects parallellizationIndeterminate iteration counts Data dependencesUsing the +Ovectorize option VectorizationF90 +O3 +Ovectorize prog.f90 Vector routines called by +OvectorizeControlling vectorization locally SaxpySdot VecdmultaddCalling Blas library routines Example 19 Example 6-1 axpy.f90REAL, External sdot Industry-wide standard VectorizationControlling code generation for performance Accessing command-line arguments Writing HP-UX applications$ fprog arg1 another arg Example 20 Example 7-1 getargs.f90Using HP-UX file I/O Stream I/O using FstreamPerforming I/O using HP-UX system calls Calling HP-UX system and library routinesUsing HP-UX file I/O Obtaining an HP-UX file descriptorCalling C routines from HP Fortran Data typesData type correspondence for HP Fortran and C Unsigned integers LogicalsSize differences between HP Fortran and C data types Size differences after compiling with +autodblComplex numbers Complex sqrcomplexCOMPLEX cmxvalExample 21 Example 8-1 passcomplex.f90 Argument-passing conventions Derived typesPointers Example 22 Example 8-2 sqrcomplex.cInteger ptr INTEGER, DIMENSION100 iarray Case sensitivityVoid fooint *ptr, int iarray100, int Call foo%REFptr, %REFiarray, %VALiExample 23 Example 8-3 sortem.c $HP$ Alias bubblesort = BubbleSort%REF,%VALExample 24 Example 8-4 testsort.f90 Case sensitivityMemory layout of a two-dimensional array in Fortran and C REAL, DIMENSION2,3,4Arrays IntExample 25 Example 8-5 passarray.f90 Example 26 Example 8-6 getarray.cStrings Null-terminated stringFortran hidden length argument Passing a stringFollowing are example C and Fortran programs StringsFile handling Example 27 Example 8-7 passchars.f90Example 28 Example 8-8 getstring.c Example 29 Example 8-9 fnumtest.f90 File handlingSharing data Int somedataExtern int somedata Extern int globals100Using Fortran directives Using HP Fortran directivesDirective syntax HP Fortran directivesSyntax Description and restrictions$HP$ Alias name = external-name arg-pass-mode-list NameLocal and global usage Case sensitivityArgument-passing conventions Strings For more informationExample 31 Example 9-1 prstr.c Example 32 Example 9-2 passstr.f90Disables the inclusion of source lines in the listing file Specified on the command lineExample 33 Example Listing fileCompatibility directives Controlling vectorizationCompatibility directives recognized by HP Fortran Vendor Directive CrayControlling parallelization Controlling dependence checksControlling checks for side effects Compatibility directivesUsing Fortran directives Command-line options not supported Migrating to HP FortranIncompatibilities with HP Fortran Compiler limitsFormat field widths Floating-point constantsIntrinsic functions Double Precision x =Procedure calls and definitions Data types and constantsInput/output DirectivesFoo**REALbar, 8 ! foo**bar KEY=Migration issues Source code issuesMigration issues MiscellaneousDirectives HP Fortran 77 directives supported by f90 optionsCommand-line option issues Intrinsic functionsConflicting intrinsics and libU77 routine names F77 options supported by f90Object code issues Data file issuesApproaches to migration HP-supplied migration tools$ fid +800 file.f $ fid +es program.f Porting to HP Fortran Compatibility extensionsCompatibility statements END structure definitionCompiler directives Compatibility directivesPointer Cray-style +Oparallel orIntrinsic procedures Nonstandard intrinsic procedures in HP FortranDirective prefixes recognized by HP Fortran +Oparallel or +OvectorizeUsing porting options Uninitialized variablesUsing porting options Large word sizeOne-trip do loops $ f90 testloop.f90Name conflicts Example 34 Example 11-1 clash.f90External int1 Names with appended underscores Source formatsPorting from Tru64 to HP Fortran Escape sequences+cfc Enhancements New optionsNof66alternate for +noonetrip Porting from Tru64 to HP FortranCheck noboundsoptions for example, -nocheckbounds +nopadsrc AltparamFortran 2003 Features Interoperability with CInput/output enhancements Miscellaneous enhancementsObject orientation features Fortran 2003 FeaturesData enhancements Documentation Feedback 153Glossary GlossarySo on. See also row-major order 155Also filename extension Memory fault 157See ttv Symbols Index159