[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-07-12 Thread tkoenig at gcc dot gnu dot org
--- Additional Comments From tkoenig at gcc dot gnu dot org 2005-07-12 20:40 --- Commit for 4.1 here: http://gcc.gnu.org/ml/gcc-cvs/2005-07/msg00486.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21593

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-07-12 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-12 20:39 --- Subject: Bug 21593 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-07-12 20:39:12 Modified files: libgfortran: ChangeLog gcc/testsuite : C

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-07-10 Thread tkoenig at gcc dot gnu dot org
--- Additional Comments From tkoenig at gcc dot gnu dot org 2005-07-10 22:18 --- The comments in fd_truncate (line 505 ff. in unix.c) read if (lseek (s->fd, s->logical_offset, SEEK_SET) == -1) return FAILURE; /* non-seekable files, like terminals and fifo's fail the lseek.

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-07-09 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-07-09 15:28 --- Subject: Re: FAIL: gfortran.dg/dev_null.f90 On Sat, Jul 09, 2005 at 02:39:34PM -, tkoenig at gcc dot gnu dot org wrote: > > > Andrew, is this sufficient to close this PR? The behavio

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-07-09 Thread tkoenig at gcc dot gnu dot org
--- Additional Comments From tkoenig at gcc dot gnu dot org 2005-07-09 14:39 --- (In reply to comment #8) > Andrew, is this sufficient to close this PR? The behavior of > ftruncate() on /dev/null appears to be system dependent. Being able to read back from /dev/null is still a bug, no

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-07-08 Thread kargl at gcc dot gnu dot org
--- Additional Comments From kargl at gcc dot gnu dot org 2005-07-08 21:01 --- I've committed FX's mainline change to dev_null.f90 that causes this test program to only be compiled on linux and solaris to the 4.0 branch. Andrew, is this sufficient to close this PR? The behavior of ftru

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-06-18 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2005-06-18 16:52 --- Subject: Re: FAIL: gfortran.dg/dev_null.f90 > The redhat system that I checked, identifies /dev/null as "a > special file" in null(4). The ftruncate man page specifically > states the behavior fo

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-06-18 Thread sgk at troutmask dot apl dot washington dot edu
--- Additional Comments From sgk at troutmask dot apl dot washington dot edu 2005-06-18 16:19 --- Subject: Re: FAIL: gfortran.dg/dev_null.f90 > int main (void) > { > int fd = open ("/dev/null", O_RDWR); > ftruncate (fd, 0); > printf ("%d\n", errno); > close (fd); > return 0;

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-06-18 Thread dave at hiauly1 dot hia dot nrc dot ca
--- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2005-06-18 15:48 --- Subject: Re: FAIL: gfortran.dg/dev_null.f90 > On linux, this code outputs 22 (EINVAL), while on freebsd it outputs 0. I > suppose the reason of the failure is similar for other platforms. It outpu

[Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90

2005-06-18 Thread fxcoudert at gcc dot gnu dot org
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-06-18 08:44 --- The problem is in the different behavior of ftruncate on /dev/null: $ cat a.c #include #include #include #include int main (void) { int fd = open ("/dev/null", O_RDWR); ftruncate (fd, 0); prin