public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46152] ALLOCATE with type-spec fails for intrinsic types
Date: Mon, 25 Oct 2010 00:34:00 -0000 [thread overview]
Message-ID: <20101025003400.Xrf5jXgE_k94J8xp6LekkNYPyicka5Lvvvnfado1C6E@z> (raw)
In-Reply-To: <bug-46152-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46152
--- Comment #9 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2010-10-25 00:33:49 UTC ---
On Sat, Oct 23, 2010 at 06:50:21PM +0000, burnus at gcc dot gnu.org wrote:
>
> Compiling the following program:
>
> implicit none ! << crucial
> integer, allocatable :: a
> allocate (integer :: a)
> end
>
> Fails with:
>
> allocate (integer :: a)
> 1
> Error: Symbol 'integer' at (1) has no IMPLICIT type
>
I believe that this is due to gfc_match_symbol() in
match_derived_type_spec(). If I understand gfc_match_symbol()
correctly, then 'integer' is added to the symbol table
of the current namespace. When match_derived_type_spec()
returns either MATCH_NO or MATCH_ERROR, it does not clean
up the namespace.
next prev parent reply other threads:[~2010-10-25 0:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 18:50 [Bug fortran/46152] New: " burnus at gcc dot gnu.org
2010-10-23 19:04 ` [Bug fortran/46152] " dominiq at lps dot ens.fr
2010-10-23 19:10 ` burnus at gcc dot gnu.org
2010-10-23 19:25 ` sgk at troutmask dot apl.washington.edu
2010-10-23 19:51 ` burnus at gcc dot gnu.org
2010-10-23 20:18 ` sgk at troutmask dot apl.washington.edu
2010-10-23 21:37 ` janus at gcc dot gnu.org
2010-10-24 7:01 ` burnus at gcc dot gnu.org
2010-10-25 0:25 ` sgk at troutmask dot apl.washington.edu
2010-10-25 0:34 ` sgk at troutmask dot apl.washington.edu [this message]
2010-10-25 0:48 ` sgk at troutmask dot apl.washington.edu
2010-10-25 4:33 ` sgk at troutmask dot apl.washington.edu
2010-10-26 4:21 ` sgk at troutmask dot apl.washington.edu
2010-10-26 19:44 ` burnus at gcc dot gnu.org
2010-10-26 21:02 ` sgk at troutmask dot apl.washington.edu
2010-10-29 14:51 ` [Bug fortran/46152] [F03] " janus at gcc dot gnu.org
2010-10-29 21:51 ` sgk at troutmask dot apl.washington.edu
2010-10-31 3:34 ` kargl at gcc dot gnu.org
2010-11-01 19:30 ` kargl at gcc dot gnu.org
2010-11-02 22:02 ` kargl at gcc dot gnu.org
2010-11-02 22:04 ` kargl 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=20101025003400.Xrf5jXgE_k94J8xp6LekkNYPyicka5Lvvvnfado1C6E@z \
--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).