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 For disk files, the segmented record is a single logical record that consists of one or more segments. Each segment is a physical record. A segmented (logical) record can exceed the absolute maximum record length (2.14 billion bytes), but each segment (physical record) individually cannot exceed the maximum record length. To access an unformatted sequential file that contains segmented records, specify FORM= ' UNFORMATTED ' and RECORDTYPE= ' SEGMENTED ' when you open the file.0 As shown in the figure below, the layout of segmented records consists of 4 bytes of control information followed by the user data: The control information consists of a 2-byte integer record size count (includes the two bytes used by the segment identifier), followed by a 2-byte integer segment identifier that identifies this segment as one of the following: Identifier Value Segment Identified 0 One of the segments between the first and last segments 1 First segment 2 Last segment 3 Only segment If the specified record length is an odd number, the user data will be padded with a single blank (one byte), but this extra byte is not added to the 2-byte integer record size count. Stream File A Stream file is not grouped into records and contains no control information. Stream files are used with CARRIAGECONTROL= ' NONE ' and contain character or binary data that is read or written only to the extent of the variables specified on the input or output statement. The figure below shows the layout of a Stream file: 172
Intel® Fortran Compiler for Linux* Systems User's Guide, Volume I: Building Applications Stream_CR and Stream_LF Records A Stream_CR or Stream_LF record is a variable-length record whose length is indicated by explicit record terminators embedded in the data, not by a count. These terminators are automatically added when you write records to a streamtype file and are removed when you read records. Each variety uses a different 1-byte record terminator: • Stream_CR files use only a carriage-return as the terminator, so Stream_CR files must not contain embedded carriage-return characters. • Stream_LF files use only a line-feed (new line) as the terminator, so Stream_LF files must not contain embedded line-feed (new line) characters. This is the usual operating system text file record type. The figure below shows the layout of Stream_CR and Stream_LF records: Microsoft* Fortran PowerStation Compatible Files When using the -fpscomp options for Microsoft* Fortran PowerStation compatibility, the following types of files are possible: • Formatted Sequential • Formatted Direct • Unformatted Sequential • Unformatted Direct Formatted Sequential Files A formatted sequential file is a series of formatted records written sequentially and read in the order in which they appear in the file. Records can vary in length 173
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:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146: Intel® Fortran Compiler for Linux*
Page 195: Intel® Fortran Compiler for Linux*
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 ...

Create successful ePaper yourself

Delete template?

Save as template?