public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46152] [F03] ALLOCATE with type-spec fails for intrinsic types
Date: Tue, 02 Nov 2010 22:02:00 -0000 [thread overview]
Message-ID: <20101102220200.Xy5XJZx8qfPO0bWaXgLPf9moEKIJigzHuz1nJT7wuTY@z> (raw)
In-Reply-To: <bug-46152-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46152
--- Comment #19 from kargl at gcc dot gnu.org 2010-11-02 22:02:42 UTC ---
Author: kargl
Date: Tue Nov 2 22:02:37 2010
New Revision: 166217
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166217
Log:
2010-10-30 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/46152
* gfortran.dg/select_type_11.f03: Update dg-error phrase.
* gfortran.dg/allocate_with_typespec_4.f90: New test.
* gfortran.dg/allocate_with_typespec_1.f90: New test.
* gfortran.dg/allocate_with_typespec_2.f: New test.
* gfortran.dg/allocate_with_typespec_3.f90: New test.
* gfortran.dg/allocate_derived_1.f90: Delete an obselescent test.
* gfortran.dg/select_type_1.f03: Update dg-error phrase.
2010-10-30 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/46152
* fortran/match.c (match_derived_type_spec): Reoplace gfc_match_symbol
with a gfc_find_symbol to prevent namespace pollution. Remove dead
code.
(match_type_spec): Remove parsing of '::'. Collapse character
kind checking to one location.
(gfc_match_allocate): Use correct locus in error message.
Added:
branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/allocate_with_typespec_1.f90
branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/allocate_with_typespec_2.f
branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/allocate_with_typespec_3.f90
branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/allocate_with_typespec_4.f90
Modified:
branches/gcc-4_5-branch/gcc/fortran/ChangeLog
branches/gcc-4_5-branch/gcc/fortran/match.c
branches/gcc-4_5-branch/gcc/testsuite/ChangeLog
branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/allocate_derived_1.f90
branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/select_type_1.f03
branches/gcc-4_5-branch/gcc/testsuite/gfortran.dg/select_type_11.f03
next prev parent reply other threads:[~2010-11-02 22:02 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
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 [this message]
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=20101102220200.Xy5XJZx8qfPO0bWaXgLPf9moEKIJigzHuz1nJT7wuTY@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).