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/22010] Namelists defined in modules not handled properly
Date: Fri, 05 Aug 2005 05:32:00 -0000 [thread overview]
Message-ID: <20050805053208.18446.qmail@sourceware.org> (raw)
In-Reply-To: <20050610195315.22010.gcc-bugzilla@chatsubo.lagged.za.net>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-08-05 05:32 -------
Subject: Bug 22010
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-4_0-branch
Changes by: pault@gcc.gnu.org 2005-08-05 05:31:44
Modified files:
gcc/fortran : module.c ChangeLog
gcc/testsuite : ChangeLog
Added files:
gcc/testsuite/gfortran.dg: namelist_use.f90
namelist_use_only.f90
Log message:
2005-08-05 Tobias Schlueter <tobias.schlueter@physik.uni-muenchen.de>
Paul Thomas <pault@gcc.gnu.org>
PR fortran/22010
Port from g95.
* module.c (mio_namelist): New function. Correct to set
namelist_tail and to give error on renaming namelist by use
association.
(mio_symbol): Call mio_namelist.
2005-08-05 Paul Thomas <pault@gcc.gnu.org>
PR fortran/22010
* gfortran.dg/namelist_use.f90: New.
* gfortran.dg/namelist_use_only.f90: New.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/module.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.31&r2=1.31.2.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.335.2.98&r2=1.335.2.99
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/namelist_use.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/namelist_use_only.f90.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=NONE&r2=1.1.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.5084.2.317&r2=1.5084.2.318
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22010
next prev parent reply other threads:[~2005-08-05 5:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 19:53 [Bug fortran/22010] New: " gcc-bugzilla at chatsubo dot lagged dot za dot net
2005-06-10 21:10 ` [Bug fortran/22010] " pinskia at gcc dot gnu dot org
2005-06-12 14:33 ` tobi at gcc dot gnu dot org
2005-06-21 21:05 ` pault at gcc dot gnu dot org
2005-08-05 5:32 ` cvs-commit at gcc dot gnu dot org [this message]
2005-08-05 5:36 ` pault at gcc dot gnu dot org
2005-08-05 15:50 ` 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=20050805053208.18446.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).