Intel(R) Fortran Compiler for Linux* Systems User's Guide Volume I ...

More documents

Recommendations

Info

Intel® Fortran Compiler for Linux* Systems User's Guide Volume I: Building Applications -v Default: Off Specifies that driver tool commands should be shown and executed. See also - dryrun. -V Default: None. Displays the compiler version information. -what Default: Off Prints the version strings of the Fortran command and the compiler. -Wl,option1[,option2,...] Default: Off Passes options (specified by option1, option2, and so forth) to the linker for processing. -X Default: Off Alternate syntax: -nostdinc Removes standard directories from the include file search. This option prevents the compiler from searching the default path specified by the FPATH environment variable. -Xlinker value Default: Off Passes value directly to the linker for processing. Optimization Options 68
Intel® Fortran Compiler for Linux* Systems User's Guide, Volume I: Building Applications The optimization options let you specify how to optimize your applications for speed, particular processors, code size, and so forth. For more information about optimization, see "Compiler Optimizations Overview" and related sections in the Intel Fortran User's Guide for Linux Volume II: Optimizing Applications. See also Floating-Point Options. Descriptions of Optimization Options -assume [no]buffered_io Default: -assume nobuffered_io (buffer is flushed as each record is written) Specifies whether records are written (flushed) to disk as each is written or are accumulated in the buffer. If you specify -assume buffered_io, records accumulate in the buffer. For disk devices, -assume buffered_io (or the equivalent OPEN statement BUFFERED='YES' specifier or the FORT_BUFFERED run-time environment variable) requests that the internal buffer will be filled, possibly by many record output statements (WRITE), before it is written to disk by the Fortran run-time system. If a file is opened for direct access, I/O buffering will be ignored. Using buffered writes usually makes disk I/O more efficient by writing larger blocks of data to the disk less often. However, if you request buffered writes, records not yet written to disk may be lost in the event of a system failure. Unless you set the FORT_BUFFERED environment variable to true, the default is BUFFERED='NO' and -assume nobuffered_io for all I/O, in which case the Fortran run-time system empties its internal buffer for each WRITE (or similar record output statements). The OPEN statement BUFFERED specifier applies to a specific logical unit. In contrast, the -assume [no]buffered_io option and the FORT_BUFFERED environment variable apply to all Fortran units. -auto_ilp32 (Itanium-based systems only) Default: Off Allows the compiler to use 32-bit pointers whenever possible as long as the application does not exceed a 32-bit address space. 69
Page 1 and 2:
Intel(R) Fortran Compiler for Linux
Page 3 and 4:
Table Of Contents Table Of Contents
Page 5 and 6:
Table Of Contents Predefined Prepro
Page 7 and 8:
Table Of Contents -e90 or -e95 ....
Page 9 and 10:
Table Of Contents -[no]fpconstant .
Page 11 and 12:
Table Of Contents -noinclude ......
Page 13 and 14:
Table Of Contents -par_threshold n.
Page 15 and 16:
Table Of Contents Using Debugger Co
Page 17 and 18:
Table Of Contents Limitations of Nu
Page 19 and 20:
Table Of Contents Specifiers for Fi
Page 21 and 22:
Table Of Contents Programming with
Page 23 and 24:
Table Of Contents Run-Time Message
Page 25 and 26:
About the Intel® Fortran Compiler
Page 27 and 28:
Intel® Fortran Compiler for Linux*
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42: Intel® Fortran Compiler for Linux*
Page 91: Intel® Fortran Compiler for Linux*
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 285 and 286:
Index ! !DEC$ prefix ..............
Page 287 and 288:
Index -assume dummy_aliases compile
Page 289 and 290:
Index common blocks allocating ....
Page 291 and 292:
Index compiler option -convert meth
Page 293 and 294:
Index additional...................
Page 295 and 296:
Index file information OPEN stateme
Page 297 and 298:
Index FOR$IOS_FLTOVF error message
Page 299 and 300:
Index FOR$IOS_TOOMANREC error messa
Page 301 and 302:
Index -fvisibility-keyword compiler
Page 303 and 304:
Index -ip_no_pinlining compiler opt
Page 305 and 306:
Index manuals additional...........
Page 307 and 308:
Index -nus compiler option.........
Page 309 and 310:
Index -pad_source compiler option..
Page 311 and 312:
Index record characteristics OPEN s
Page 313 and 314:
Index signal routine calling ......
Page 315 and 316:
Index uninstall.sh file ...........
show all

Intel(R) Fortran Compiler for Linux* Systems User's Guide Volume I ...

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

Delete template?

Save as template?