https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70684
--- Comment #12 from Andy May <ajmay81 at googlemail dot com> --- I don't know that it's necessary or desired to support both '\n' and '\r' as eol, but instead the native eol just needs to be used consistently everywhere, for example something like the following pseudo code: #ifdef __MINGW32__ #define EOL '\r' #else #define EOL '\n' #endif ... dtp->u.p.at_eol = (c == EOL || c == EOF); As mentioned in this ifort thread: https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268116 you might really want to read the 'wrong' eol as data. If one wants to move a file generated on one OS to another there are tools already existing to change the line endings.
