public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32876] Wrongly accepts private items in public NAMELISTs
Date: Sat, 28 Jul 2007 08:51:00 -0000 [thread overview]
Message-ID: <20070728085122.12337.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32876-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from dfranke at gcc dot gnu dot org 2007-07-28 08:51 -------
Subject: Bug 32876
Author: dfranke
Date: Sat Jul 28 08:51:06 2007
New Revision: 127014
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127014
Log:
gcc/fortran:
2007-07-28 Daniel Franke <franke.daniel@gmail.com>
PR fortran/31818
PR fortran/32876
PR fortran/32905
* gfortran.h (symbol_attribute): Added bits for pointer_comp,
private_comp.
* parse.c (parse_derived): Set pointer_comp/private_comp bits if the
derived
type ultimately contains pointer components or private components.
* module.c (ab_attribute): New values AB_POINTER_COMP, AB_PRIVATE_COMP.
(attr_bits): Added names for new ab_attributes.
(mio_symbol_attribute): Save/restore new attribute bits in modules.
* match.c (gfc_match_namelist): Removed check for namelist objects of
assumed
shape.
* resolve.c (resolve_fl_namelist): Added check for pointer or private
components in nested types. Added check for namelist objects of assumed
shape.
gcc/testsuite:
2007-07-28 Daniel Franke <franke.daniel@gmail.com>
* gfortran.dg/namelist_5.f90: Adjusted error message.
* gfortran.dg/assumed_shape_nml.f90: Renamed to ...
* gfortran.dg/namelist_31.f90: ... this. Removed dg-warning directive.
* gfortran.dg/assumed_size_nml.f90: Renamed to ...
* gfortran.dg/namelist_32.f90: ... this.
PR fortran/32876
* gfortran.dg/namelist_33.f90: New test.
PR fortran/32905
* gfortran.dg/namelist_34.f90: New test.
PR fortran/31818
* gfortran.dg/namelist_35.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/namelist_31.f90
- copied, changed from r126930,
trunk/gcc/testsuite/gfortran.dg/assumed_shape_nml.f90
trunk/gcc/testsuite/gfortran.dg/namelist_32.f90
- copied unchanged from r126930,
trunk/gcc/testsuite/gfortran.dg/assumed_size_nml.f90
trunk/gcc/testsuite/gfortran.dg/namelist_33.f90
trunk/gcc/testsuite/gfortran.dg/namelist_34.f90
trunk/gcc/testsuite/gfortran.dg/namelist_35.f90
Removed:
trunk/gcc/testsuite/gfortran.dg/assumed_shape_nml.f90
trunk/gcc/testsuite/gfortran.dg/assumed_size_nml.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/match.c
trunk/gcc/fortran/module.c
trunk/gcc/fortran/parse.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/namelist_5.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32876
next prev parent reply other threads:[~2007-07-28 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 13:43 [Bug fortran/32876] New: " burnus at gcc dot gnu dot org
2007-07-25 5:13 ` [Bug fortran/32876] " pault at gcc dot gnu dot org
2007-07-25 17:57 ` dfranke at gcc dot gnu dot org
2007-07-25 18:09 ` burnus at gcc dot gnu dot org
2007-07-28 8:51 ` dfranke at gcc dot gnu dot org [this message]
2007-07-28 8:54 ` dfranke 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=20070728085122.12337.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).