public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/13278] derived type namelist I/O support missing, causes ICE
Date: Wed, 18 Aug 2004 01:20:00 -0000 [thread overview]
Message-ID: <20040818012010.19241.qmail@sourceware.org> (raw)
In-Reply-To: <20031203084834.13278.steven@gcc.gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-08-18 01:20 -------
Subject: Bug 13278
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: pbrook@gcc.gnu.org 2004-08-18 01:20:06
Modified files:
gcc/fortran : ChangeLog trans-io.c
libgfortran : ChangeLog
libgfortran/io : io.h transfer.c write.c
Log message:
2004-08-18 Victor Leikehman <lei@il.ibm.com>
PR fortran/13278
* trans-io.c (transfer_namelist_element): New. Recursively handle
derived-type variables. Pass string lengths.
(build_dt): Code moved to build_namelist, with some
changes and additions.
(gfc_build_io_library_fndecls): Declare the fifth
argument in st_set_nml_var_char -- string_length.
libgfortran/
* io/transfer.c (st_set_nml_var)
* io/write.c (namelist_write): Allow var_name and var_name_len to be
null. For strings, use string_length field instead of len.
* io/io.h (struct namelist_type): New field string_length.
(st_set_nml_var_char): New argument string_length.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.152&r2=1.153
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-io.c.diff?cvsroot=gcc&r1=1.10&r2=1.11
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.61&r2=1.62
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/io.h.diff?cvsroot=gcc&r1=1.6&r2=1.7
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&r1=1.8&r2=1.9
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/write.c.diff?cvsroot=gcc&r1=1.9&r2=1.10
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13278
next prev parent reply other threads:[~2004-08-18 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 8:48 [Bug fortran/13278] New: [gfortan] derived type " steven at gcc dot gnu dot org
2003-12-05 23:15 ` [Bug fortran/13278] " pinskia at gcc dot gnu dot org
2003-12-28 3:02 ` pinskia at gcc dot gnu dot org
2004-01-20 15:17 ` pinskia at gcc dot gnu dot org
2004-05-18 13:41 ` [Bug fortran/13278] [gfortran] " pinskia at gcc dot gnu dot org
2004-06-02 13:56 ` [Bug fortran/13278] [gfortran] derived type namelist " tobi at gcc dot gnu dot org
2004-06-28 7:28 ` [Bug fortran/13278] " pinskia at gcc dot gnu dot org
2004-08-16 18:43 ` pinskia at gcc dot gnu dot org
2004-08-18 1:20 ` cvs-commit at gcc dot gnu dot org [this message]
2004-08-18 2:22 ` pinskia at gcc dot gnu dot org
2004-08-25 16:59 ` 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=20040818012010.19241.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).