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/42420] libgfortran fails to open large files on MINGW32
Date: Fri, 18 Dec 2009 06:43:00 -0000 [thread overview]
Message-ID: <20091218064302.28912.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42420-11807@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from kargl at gcc dot gnu dot org 2009-12-18 06:43 -------
(In reply to comment #3)
> No,
>
> this was the trunk from yesterday. Some wrinkeles seem to remain...
>
You should have included this information in your
original bug report. I won't have wasted my time
looking up Janne's commit message and replying to
your bug report.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42420
next prev parent reply other threads:[~2009-12-18 6:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 0:24 [Bug libfortran/42420] New: " jpr at csc dot fi
2009-12-18 0:35 ` [Bug libfortran/42420] " jpr at csc dot fi
2009-12-18 0:58 ` kargl at gcc dot gnu dot org
2009-12-18 5:43 ` jpr at csc dot fi
2009-12-18 6:43 ` kargl at gcc dot gnu dot org [this message]
2009-12-18 8:51 ` burnus at gcc dot gnu dot org
2009-12-20 10:23 ` jb at gcc dot gnu dot org
2010-01-02 21:39 ` jb at gcc dot gnu dot org
2010-01-03 18:09 ` jb at gcc dot gnu dot org
2010-01-05 19:14 ` jb 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=20091218064302.28912.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).