Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Can ifort handle unformatted files that are both big_endian and little_endian

crtierney42
New Contributor I
‎06-06-2008 11:55 AM
1,080 Views

I have received some data files that have been difficult to read. It turns out that the data in the file are little endian, but the Fortran record indicators are big_endian. I can't go back to the source and figure out what they were doing. I am pretty sure the files were generated on an IBM Power system under AIX (but I am not positive).

Is there a way to tell the compiler to read the record indicators as one endian type, but the data as another?

Thanks,
Craig

0 Kudos

Link Copied

2 Replies
Steven_L_Intel1
Employee
‎06-06-2008 05:50 PM
1,080 Views
No, sorry. I'd be very curious to know the details of how such a file was constructed - I haven't run into such a combination before.

The best I can suggest is to write some routines to do the byte swapping after you read the data.
0 Kudos
Copy link
crtierney42
New Contributor I
‎06-10-2008 11:14 AM
1,080 Views
It came from an IBM Power system. I think that the data were generated by a C routine that mimicked creation of an unformatted fortran file. I found someone who wrote a code to do the conversion for this data.


0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.