From: Janus Weil <janus@gcc.gnu.org>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, libfortran] Fix PR 30162, write with pipes
Date: Sat, 15 Dec 2012 12:32:00 -0000 [thread overview]
Message-ID: <CAKwh3qgEMjx0Z4=QNQf2n=r-cGMtHuisYUcwSz98SZmHUprKvA@mail.gmail.com> (raw)
In-Reply-To: <50CC5A5B.8030603@netcologne.de>
Hi Thomas,
wrong patch attached? It contains a hunk in frontend-passes.c, which
seems totally unrelated ...
Cheers,
Janus
2012/12/15 Thomas Koenig <tkoenig@netcologne.de>:
> Hello world,
>
> the attached patch fixes the regression and regtests cleanly.
> No test case because I could not find anything portable
> to create a FIFO in the testsuite.
>
> OK for trunk and 4.7?
>
> Thomas
>
> 2012-12-15 Thomas Koenig <tkoenig@gcc.gnu.org>
>
> PR libfortran/30162
> * io/unix.c (raw_tell): If the lseek is done on a
> non-seekable file, return 0.
>
next prev parent reply other threads:[~2012-12-15 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 11:09 Thomas Koenig
2012-12-15 12:32 ` Janus Weil [this message]
2012-12-15 12:44 ` Thomas Koenig
2012-12-20 11:23 ` *ping* " Thomas Koenig
2012-12-21 20:41 ` Jerry DeLisle
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='CAKwh3qgEMjx0Z4=QNQf2n=r-cGMtHuisYUcwSz98SZmHUprKvA@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).