public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/21593] FAIL: gfortran.dg/dev_null.f90
Date: Fri, 08 Jul 2005 21:19:00 -0000 [thread overview]
Message-ID: <20050708210139.9157.qmail@sourceware.org> (raw)
In-Reply-To: <20050515210432.21593.danglin@gcc.gnu.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
ftruncate() on /dev/null appears to be system dependent.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21593
next prev parent reply other threads:[~2005-07-08 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 21:04 [Bug fortran/21593] New: " danglin at gcc dot gnu dot org
2005-05-17 8:04 ` [Bug fortran/21593] " fxcoudert at gcc dot gnu dot org
2005-05-22 18:20 ` fxcoudert at gcc dot gnu dot org
2005-05-22 18:20 ` fxcoudert at gcc dot gnu dot org
2005-06-18 8:44 ` [Bug libfortran/21593] " fxcoudert at gcc dot gnu dot org
2005-06-18 15:48 ` dave at hiauly1 dot hia dot nrc dot ca
2005-06-18 16:19 ` sgk at troutmask dot apl dot washington dot edu
2005-06-18 16:52 ` dave at hiauly1 dot hia dot nrc dot ca
2005-07-08 21:19 ` kargl at gcc dot gnu dot org [this message]
2005-07-09 15:06 ` tkoenig at gcc dot gnu dot org
2005-07-09 15:48 ` sgk at troutmask dot apl dot washington dot edu
2005-07-10 22:23 ` tkoenig at gcc dot gnu dot org
2005-07-12 20:39 ` cvs-commit at gcc dot gnu dot org
2005-07-12 20:45 ` tkoenig at gcc dot gnu dot org
2005-07-13 3:12 ` [Bug libfortran/21593] [4.0 only] " pinskia at gcc dot gnu dot org
2005-07-19 18:07 ` cvs-commit at gcc dot gnu dot org
2005-07-19 18:35 ` tkoenig at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050708210139.9157.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).