From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 347 invoked by alias); 9 Jul 2005 15:28:50 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 314 invoked by alias); 9 Jul 2005 15:28:48 -0000 Date: Sat, 09 Jul 2005 15:48:00 -0000 Message-ID: <20050709152848.312.qmail@sourceware.org> From: "sgk at troutmask dot apl dot washington dot edu" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050515210432.21593.danglin@gcc.gnu.org> References: <20050515210432.21593.danglin@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90 X-Bugzilla-Reason: CC X-SW-Source: 2005-07/txt/msg01103.txt.bz2 List-Id: ------- 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 -0000, tkoenig at gcc dot gnu dot org wrote: > > > 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 matter > what ftruncate() does. > It's system dependent in that reading or writing /dev/null always succeeds (at least on *BSD). You can't check the return value or errno to see if there is some failure. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21593