[Bug other/43955] linux hard lock-up when gcc output file is on filesystem with insufficient disk space

[jsm28 at gcc dot gnu dot org]

------- Comment #7 from jsm28 at gcc dot gnu dot org  2010-05-02 11:45 -------
It is the responsibility of your filesystem to ensure that write or close
return error status if there isn't sufficient disk space; if they do not,
this is a kernel bug.  Most applications should never call fsync; that's only
if the application is meant to be making data integrity guarantees across
unclean shutdown, and it never makes sense to make such guarantees for
compiler and assembler output since those files can always be recreated from
the associated input files; it doesn't matter if the last few seconds'
compilation output before a crash is lost or corrupted.


-- 

jsm28 at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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