Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29390 Discussions

Formatted Direct access files cr/lf different in Debug/Release

NotThatItMatters
Beginner
1,520 Views

Using the command

        OPEN(UNIT = 9, FILE = FILLIN, RECL = 200, FORM = 'FORMATTED', &
          ACCESS = 'DIRECT')

I get a file with CR/LF ending the 200 byte records in Release whereas the file has only CR (or maybe just LF) in Debug.  Why?

0 Kudos
1 Solution
Steven_L_Intel1
Employee
1,520 Views

Compare the project options - there is probably one you have set in one configuration and not the other. I would look specifically at /fpscomp.

View solution in original post

0 Kudos
5 Replies
Steven_L_Intel1
Employee
1,521 Views

Compare the project options - there is probably one you have set in one configuration and not the other. I would look specifically at /fpscomp.

0 Kudos
NotThatItMatters
Beginner
1,520 Views

I am noting the Release executable has the options

/fpscomp:ioformat /fpscomp:ldio_spacing /fpscomp:general

whereas the Debug executable does not.  Are these the cause (or the savior)?

0 Kudos
Steven_L_Intel1
Employee
1,520 Views

Yep. It's /fpscomp:general that is causing the difference.

0 Kudos
NotThatItMatters
Beginner
1,520 Views

That did the trick, putting /fpscomp:general as an "AdditionalOption" in the debug executable.

Thank you.

Most of these options are legacy, as in were implemented before I saw the code 8 years ago.  Where might the documentation on such things be?

0 Kudos
Steven_L_Intel1
Employee
1,520 Views

Same place as the other options - in the compiler documentation. Look in the index under /fpscomp.

0 Kudos
Reply