public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41587] [OOP] ICE with ALLOCATABLE CLASS components
Date: Sat, 17 Oct 2009 18:10:00 -0000 [thread overview]
Message-ID: <20091017180944.3849.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41587-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pault at gcc dot gnu dot org 2009-10-17 18:09 -------
Subject: Bug 41587
Author: pault
Date: Sat Oct 17 18:09:25 2009
New Revision: 152955
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152955
Log:
2009-10-17 Janus Weil <janus@gcc.gnu.org>
Paul Thomas <pault@gcc.gnu.org>
PR fortran/41608
* decl.c (gfc_match_data_decl): Add BT_CLASS for undefined type
and empty type errors.
* parse.c (gfc_build_block_ns): Only set recursive if parent ns
has a proc_name.
PR fortran/41629
PR fortran/41618
PR fortran/41587
* gfortran.h : Add class_ok bitfield to symbol_attr.
* decl.c (build_sym): Set attr.class_ok if dummy, pointer or
allocatable.
(build_struct): Use gfc_try 't' to carry errors past the call
to encapsulate_class_symbol.
(attr_decl1): For a CLASS object, apply the new attribute to
the data component.
* match.c (gfc_match_select_type): Set attr.class_ok for an
assigned selector.
* resolve.c (resolve_fl_variable_derived): Check a CLASS object
is dummy, pointer or allocatable by testing the class_ok and
the use_assoc attribute.
2009-10-17 Janus Weil <janus@gcc.gnu.org>
Paul Thomas <pault@gcc.gnu.org>
PR fortran/41629
* gfortran.dg/class_6.f90: New test.
PR fortran/41608
PR fortran/41587
* gfortran.dg/class_7.f90: New test.
PR fortran/41618
* gfortran.dg/class_8.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/class_6.f03
trunk/gcc/testsuite/gfortran.dg/class_7.f03
trunk/gcc/testsuite/gfortran.dg/class_8.f03
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/decl.c
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/match.c
trunk/gcc/fortran/parse.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41587
next prev parent reply other threads:[~2009-10-17 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 13:31 [Bug fortran/41587] New: " burnus at gcc dot gnu dot org
2009-10-14 8:42 ` [Bug fortran/41587] " dominiq at lps dot ens dot fr
2009-10-17 18:10 ` pault at gcc dot gnu dot org [this message]
2009-10-18 12:25 ` pault at gcc dot gnu dot org
[not found] <bug-41587-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 23:13 ` mikael at gcc dot gnu.org
2012-02-02 23:37 ` mikael at gcc dot gnu.org
2012-02-03 7:35 ` burnus at gcc dot gnu.org
2012-02-06 14:21 ` pault at gcc dot gnu.org
2012-04-23 12:59 ` burnus at gcc dot gnu.org
2012-05-06 20:33 ` burnus at gcc dot gnu.org
2012-05-06 20:49 ` burnus at gcc dot gnu.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=20091017180944.3849.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).