This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libfortran/24919] CRLF support in libgfortran



------- Comment #16 from fxcoudert at gcc dot gnu dot org  2005-11-27 11:42 -------
Subject: Bug 24919

Author: fxcoudert
Date: Sun Nov 27 11:42:46 2005
New Revision: 107563

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107563
Log:
        PR libfortran/24919

        * io/list_read.c (eat_separator, finish_separator,
        read_character): Handle CRLF separators correctly during reads.
        (nml_query): Use the HAVE_CRLF macro to print adequate newlines.
        * io/io.h (st_parameter_dt): Add comment about the possible
        values for sf_seen_eor.
        * io/unix.c (tempfile, regular_file): HAVE_CRLF doesn't imply
        that O_BINARY is defined, so we add that condition.
        (stream_at_bof): Fix typo in comment.
        * io/transfer.c (read_sf): Handle correctly CRLF, setting
        sf_seen_eor value to 2 instead of 1.
        (formatted_transfer_scalar): Use the sf_seen_eor value to
        handle CRLF the right way.
        * io/write.c (nml_write_obj, namelist_write): Use CRLF as newline
        when HAVE_CRLF is defined.

        * gfortran.dg/ftell_1.f90: Modify testcase so that it doesn't
        fail on CRLF platforms.
        * gfortran.dg/ftell_2.f90: Likewise.

Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/ftell_1.f90
    trunk/gcc/testsuite/gfortran.dg/ftell_2.f90
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/io.h
    trunk/libgfortran/io/list_read.c
    trunk/libgfortran/io/transfer.c
    trunk/libgfortran/io/unix.c
    trunk/libgfortran/io/write.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24919


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]