public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wf_cs at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/16531] [gfortran] Hollerith Data not supported
Date: Mon, 28 Feb 2005 15:54:00 -0000 [thread overview]
Message-ID: <20050228103012.9649.qmail@sourceware.org> (raw)
In-Reply-To: <20040713205527.16531.wkpark@kldp.org>
------- Additional Comments From wf_cs at yahoo dot com 2005-02-28 10:30 -------
(In reply to comment #3)
> Is anyone working on this? It is blocking some significant codes I am
testing.
Yes. I have worked it out. I am waiting for the committing of my patch for
PR18827 which blocks this fixing.
If you like, you can try this patch. But you need apply the patch I posted in
the message: http://gcc.gnu.org/ml/fortran/2005-02/msg00255.html first. Or you
will fail to patch. Welcom to use and test.
Best Regards,
Feng Wang
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16531
next prev parent reply other threads:[~2005-02-28 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 20:55 [Bug fortran/16531] New: Hollerith Data does " wkpark at kldp dot org
2004-07-13 22:38 ` [Bug fortran/16531] " pinskia at gcc dot gnu dot org
2004-12-27 8:13 ` wf_cs at yahoo dot com
2005-01-06 14:41 ` tobi at gcc dot gnu dot org
2005-02-28 3:06 ` [Bug fortran/16531] [gfortran] Hollerith Data " jvdelisle at verizon dot net
2005-02-28 15:54 ` wf_cs at yahoo dot com [this message]
2005-04-08 11:47 ` pinskia at gcc dot gnu dot org
2005-07-07 7:56 ` cvs-commit at gcc dot gnu dot org
2005-07-07 9:47 ` [Bug fortran/16531] [4.0 only, gfortran] " fengwang at gcc dot gnu dot org
2005-07-07 13:24 ` pinskia at gcc dot gnu dot org
2005-07-12 1:51 ` cvs-commit at gcc dot gnu dot org
2005-07-12 4:26 ` pinskia 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=20050228103012.9649.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).