public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iliev at rz dot rwth-aachen.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/30162] I/O with named pipes does not work
Date: Thu, 02 Aug 2012 17:34:00 -0000 [thread overview]
Message-ID: <bug-30162-4-cDiKQrbjkE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-30162-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30162
Hristo Iliev <iliev at rz dot rwth-aachen.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iliev at rz dot
| |rwth-aachen.de
--- Comment #22 from Hristo Iliev <iliev at rz dot rwth-aachen.de> 2012-08-02 17:34:03 UTC ---
Revision 180701 removed all checks for special files in unit.c:unit_truncate().
As a consequence programs compiled with gfortran 4.6.3 and newer cannot to
write (formatted) to Unix named pipes as ftruncate() fails with EINVAL:
(64-bit code)
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, " Hello, world!\n", 15) = 15
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
ftruncate(3, 18446744073709551615) = -1 EINVAL (Invalid argument)
(32-bit code)
_llseek(3, 0, 0xffba8fa0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, " Hello, world!\n", 15) = 15
_llseek(3, 0, 0xffba9080, SEEK_CUR) = -1 ESPIPE (Illegal seek)
ftruncate64(3, 18446744073709551615) = -1 EINVAL (Invalid argument)
next parent reply other threads:[~2012-08-02 17:34 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-30162-4@http.gcc.gnu.org/bugzilla/>
2012-08-02 17:34 ` iliev at rz dot rwth-aachen.de [this message]
2012-08-03 19:45 ` jb at gcc dot gnu.org
2012-08-06 13:43 ` burnus at gcc dot gnu.org
2012-10-30 11:37 ` [Bug libfortran/30162] [4.7/4.8 Regression] " burnus at gcc dot gnu.org
2012-11-10 14:38 ` tkoenig at gcc dot gnu.org
2012-11-10 20:22 ` jb at gcc dot gnu.org
2012-11-20 12:19 ` jakub at gcc dot gnu.org
2012-11-24 12:06 ` tkoenig at gcc dot gnu.org
2012-11-25 15:08 ` jb at gcc dot gnu.org
2012-12-14 23:09 ` tkoenig at gcc dot gnu.org
2012-12-15 11:04 ` tkoenig at gcc dot gnu.org
2012-12-21 20:51 ` tkoenig at gcc dot gnu.org
2012-12-22 10:47 ` tkoenig at gcc dot gnu.org
2012-12-22 10:49 ` tkoenig at gcc dot gnu.org
2012-12-22 12:03 ` dominiq at lps dot ens.fr
2012-12-22 15:38 ` tkoenig at netcologne dot de
2012-12-22 19:13 ` dominiq at lps dot ens.fr
2012-12-22 20:16 ` tkoenig at netcologne dot de
2012-12-22 21:23 ` dominiq at lps dot ens.fr
2012-12-22 22:15 ` tkoenig at gcc dot gnu.org
2012-12-23 14:17 ` dominiq at lps dot ens.fr
2012-12-23 15:10 ` tkoenig at netcologne dot de
2012-12-25 15:27 ` tkoenig at gcc dot gnu.org
2013-02-17 20:11 ` [Bug libfortran/30162] [4.7/4.8 Regression] I/O with named pipes does not work on Darwin dominiq at lps dot ens.fr
2013-02-18 18:44 ` tkoenig at gcc dot gnu.org
2013-02-18 19:16 ` dominiq at lps dot ens.fr
2013-02-18 20:17 ` jb at gcc dot gnu.org
2013-02-18 21:25 ` tkoenig at netcologne dot de
2013-02-18 21:29 ` tkoenig at netcologne dot de
2013-02-18 21:47 ` [Bug libfortran/30162] [4.7/4.8 Regression] Unformatted sequential I/O with named pipes does not work tkoenig at gcc dot gnu.org
2013-02-19 10:59 ` jb at gcc dot gnu.org
2013-02-19 22:49 ` jb at gcc dot gnu.org
2013-02-21 19:03 ` jb at gcc dot gnu.org
2013-02-21 20:13 ` jb at gcc dot gnu.org
2013-02-21 20:40 ` jb at gcc dot gnu.org
2013-02-22 8:54 ` burnus at gcc dot gnu.org
2013-04-11 7:58 ` [Bug libfortran/30162] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2013-08-09 9:25 ` [Bug libfortran/30162] Document when sequential I/O with named pipes works tkoenig at gcc dot gnu.org
2015-02-01 13:20 ` jvdelisle at gcc dot gnu.org
2006-12-12 4:28 [Bug libfortran/30162] New: I/O with named pipes does not work jvdelisle at gcc dot gnu dot org
2006-12-15 21:15 ` [Bug libfortran/30162] " tkoenig at gcc dot gnu dot org
2006-12-16 11:44 ` tkoenig at gcc dot gnu dot org
2006-12-16 21:34 ` tkoenig at gcc dot gnu dot org
2006-12-28 21:22 ` tkoenig at gcc dot gnu dot org
2006-12-28 21:39 ` tkoenig at gcc dot gnu dot org
2006-12-28 23:11 ` jvdelisle at gcc dot gnu dot org
2006-12-29 9:51 ` tkoenig at gcc dot gnu dot org
2007-01-01 4:59 ` jvdelisle at gcc dot gnu dot org
2007-01-01 15:17 ` tkoenig at gcc dot gnu dot org
2007-01-01 17:51 ` jvdelisle at gcc dot gnu dot org
2007-01-02 22:09 ` tkoenig at gcc dot gnu dot org
2007-01-05 5:00 ` patchapp at dberlin dot org
2007-01-06 0:14 ` jvdelisle at gcc dot gnu dot org
2007-01-06 21:08 ` jvdelisle at gcc dot gnu dot org
2007-01-06 22:27 ` tkoenig at gcc dot gnu dot org
2007-01-07 1:34 ` jvdelisle at gcc dot gnu dot org
2007-02-01 7:20 ` jvdelisle at gcc dot gnu dot org
2007-02-01 9:28 ` burnus at gcc dot gnu dot org
2007-02-02 2:00 ` jvdelisle at gcc dot gnu dot org
2007-08-18 19:07 ` dagurasu15 at hotmail dot com
2007-08-18 19:08 ` dagurasu15 at hotmail dot com
2007-08-18 19:39 ` jvdelisle at gcc dot gnu dot org
2007-08-19 19:46 ` jvdelisle 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=bug-30162-4-cDiKQrbjkE@http.gcc.gnu.org/bugzilla/ \
--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).