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/30554] [4.2 and 4.1 only] ICE in mio_pointer_ref at module.c:1945
Date: Sat, 17 Feb 2007 17:17:00 -0000 [thread overview]
Message-ID: <20070217171711.29175.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30554-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #15 from pault at gcc dot gnu dot org 2007-02-17 17:17 -------
Subject: Bug 30554
Author: pault
Date: Sat Feb 17 17:16:56 2007
New Revision: 122074
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122074
Log:
2007-02-17 Paul Thomas <pault@gcc.gnu.org>
PR fortran/30554
* module.c (find_symtree_for_symbol): New function to return
a symtree that is not a "unique symtree" given a symbol.
(read_module): Do not automatically set pointer_info to
referenced, if the symbol has a namespace, because this
inhibits the generation of a unique symtree. Recycle the
symtree if possible by calling find_symtree_for_symbol. If a
symbol is excluded by an ONLY clause, check to see if there is
a symtree already loaded. If so, attach the symtree to the
pointer_info.
PR fortran/30319
* decl.c (add_init_expr_to_sym): Make new charlen for an array
constructor initializer.
2007-02-17 Paul Thomas <pault@gcc.gnu.org>
PR fortran/30554
* gfortran.dg/used_dummy_types_6.f90: New test.
* gfortran.dg/used_dummy_types_7.f90: New test..
PR fortran/30617
* gfortran.dg/intrinsic_actual_2.f90: Make this legal fortran
by getting rid of recursive I/O and providing functions with
results.
PR fortran/30319
* gfortran.dg/char_array_constructor_2.f90
Added:
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/char_array_constructor_2.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/used_dummy_types_6.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/used_dummy_types_7.f90
Modified:
branches/gcc-4_2-branch/gcc/fortran/ChangeLog
branches/gcc-4_2-branch/gcc/fortran/decl.c
branches/gcc-4_2-branch/gcc/fortran/module.c
branches/gcc-4_2-branch/gcc/testsuite/ChangeLog
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/intrinsic_actual_2.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30554
next prev parent reply other threads:[~2007-02-17 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 9:48 [Bug fortran/30554] New: " burnus at gcc dot gnu dot org
2007-01-23 10:34 ` [Bug fortran/30554] " burnus at gcc dot gnu dot org
2007-01-23 13:30 ` fxcoudert at gcc dot gnu dot org
2007-01-23 20:56 ` burnus at gcc dot gnu dot org
2007-01-28 8:04 ` pault at gcc dot gnu dot org
2007-01-28 12:30 ` patchapp at dberlin dot org
2007-01-28 13:40 ` pault at gcc dot gnu dot org
2007-01-29 10:28 ` pault at gcc dot gnu dot org
2007-02-02 9:27 ` [Bug fortran/30554] [4.2 and 4.1 only] " jellby at yahoo dot com
2007-02-02 10:03 ` burnus at gcc dot gnu dot org
2007-02-03 7:26 ` pault at gcc dot gnu dot org
2007-02-03 21:11 ` pault at gcc dot gnu dot org
2007-02-04 12:05 ` pault at gcc dot gnu dot org
2007-02-09 12:20 ` patchapp at dberlin dot org
2007-02-11 20:59 ` pault at gcc dot gnu dot org
2007-02-12 23:40 ` pault at gcc dot gnu dot org
2007-02-17 17:17 ` pault at gcc dot gnu dot org [this message]
2007-02-17 17:18 ` [Bug fortran/30554] [4.1 " pault 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=20070217171711.29175.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).