[Bug fortran/43032] New: FLUSH: Document that it does not call fsync() but fflush()

[Bug fortran/43032] New: FLUSH: Document that it does not call fsync() but fflush()

[burnus at gcc dot gnu dot org]

http://gcc.gnu.org/onlinedocs/gfortran/FLUSH.html has:

"Flushes Fortran unit(s) currently open for output. [...] Beginning with the
Fortran 2003 standard, there is a FLUSH statement that should be preferred over
the FLUSH intrinsic"

However, it is left unclear whether fflush() or fsync() is called by the
Fortran run-time library. (Answer: fflush(); cf. also
http://gcc.gnu.org/ml/fortran/2010-02/msg00074.html)

Expected: The documentation makes clear that "only" fflush() is called and
points out that "fsync" (with the proper interface) can be called using FNUM.
Actually, the example could be enhanced.

POSIX (SUV) has for fflush:
       If  stream  points  to  an output stream or an update stream in which
the most recent
       operation was not input, fflush() shall cause any unwritten data for
that  stream  to
       be  written to the file,  and the st_ctime and st_mtime fields of the
underlying file
       shall be marked for update.
and for fsync:
       The  fsync()  function shall request that all data for the open file
descriptor named
       by fildes is to be transferred  to  the  storage  device  associated 
with  the  file
       described  by  fildes in an implementation-defined manner. The fsync()
function shall
       not return until the system has completed that action or until an error
is  detected.


-- 
           Summary: FLUSH: Document that it does not call fsync() but
                    fflush()
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: documentation
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


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

[Bug fortran/43032] FLUSH: Document that it does not call fsync() but fflush()

[fxcoudert at gcc dot gnu dot org]

------- Comment #1 from fxcoudert at gcc dot gnu dot org  2010-06-10 12:47 -------
Patch submitted at: http://gcc.gnu.org/ml/fortran/2010-06/msg00091.html


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |fxcoudert at gcc dot gnu dot
                   |dot org                     |org
                URL|                            |http://gcc.gnu.org/ml/fortra
                   |                            |n/2010-06/msg00091.html
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
           Keywords|                            |patch
   Last reconfirmed|0000-00-00 00:00:00         |2010-06-10 12:47:34
               date|                            |


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

[Bug fortran/43032] FLUSH: Document that it does not call fsync() but fflush()

[fxcoudert at gcc dot gnu dot org]

------- Comment #2 from fxcoudert at gcc dot gnu dot org  2010-06-10 19:14 -------
Subject: Bug 43032

Author: fxcoudert
Date: Thu Jun 10 19:14:12 2010
New Revision: 160568

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=160568
Log:
        PR fortran/43032
        * intrinsic.texi (FLUSH): Note the difference between FLUSH and
        POSIX's fsync(), and how to call the latter from Fortran code.

Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/intrinsic.texi


-- 


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

[Bug fortran/43032] FLUSH: Document that it does not call fsync() but fflush()

[fxcoudert at gcc dot gnu dot org]

------- Comment #3 from fxcoudert at gcc dot gnu dot org  2010-06-10 19:15 -------
Fixed.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


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