public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43062] NAMELIST attribute conflicts with ALLOCATABLE attribute
Date: Wed, 02 Feb 2011 17:59:00 -0000 [thread overview]
Message-ID: <bug-43062-4-bpsKiE0R8E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43062-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43062
--- Comment #29 from Diego Novillo <dnovillo at gcc dot gnu.org> 2011-02-02 17:52:20 UTC ---
Author: dnovillo
Date: Wed Feb 2 17:52:14 2011
New Revision: 169614
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=169614
Log:
2011-01-26 Tobias Burnus <burnus@net-b.de>
PR fortran/47339
PR fortran/43062
* match.c (gfc_match_namelist): Allow assumed-length characters.
* resolve.c (resolve_fl_namelist): Adapt and add error messages.
* symbol.c (check_conflict): Allow allocatables in NML for
* F2003.
* trans-io.c (nml_get_addr_expr,transfer_namelist_element):
Changes due to that change.
2011-01-26 Tobias Burnus <burnus@net-b.de>
PR fortran/47339
PR fortran/43062
* fortran.dg/namelist_69.f90: New test.
* fortran.dg/namelist_70.f90: New test.
* fortran.dg/namelist_assumed_char.f90: Modify dg-error, augment
* test.
* fortran.dg/namelist_3.f90: Adapt test.
* fortran.dg/namelist_34.f90: Ditto.
* fortran.dg/namelist_35.f90: Ditto.
* fortran.dg/namelist_5.f90: Ditto.
* fortran.dg/namelist_63.f90: Ditto.
* gfortran.dg/alloc_comp_constraint_1.f90: Ditto.
Added:
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_69.f90
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_70.f90
Modified:
branches/google/integration/gcc/fortran/match.c
branches/google/integration/gcc/fortran/resolve.c
branches/google/integration/gcc/fortran/symbol.c
branches/google/integration/gcc/fortran/trans-io.c
branches/google/integration/gcc/testsuite/gfortran.dg/alloc_comp_constraint_1.f90
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_3.f90
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_34.f90
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_35.f90
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_5.f90
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_63.f90
branches/google/integration/gcc/testsuite/gfortran.dg/namelist_assumed_char.f90
next prev parent reply other threads:[~2011-02-02 17:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43062-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 20:21 ` jvdelisle at gcc dot gnu.org
2010-10-02 6:44 ` burnus at gcc dot gnu.org
2011-01-18 13:07 ` burnus at gcc dot gnu.org
2011-01-18 13:40 ` zazzou at gmail dot com
2011-01-18 13:40 ` jvdelisle at gcc dot gnu.org
2011-01-22 21:58 ` burnus at gcc dot gnu.org
2011-01-22 22:41 ` burnus at gcc dot gnu.org
2011-01-26 10:33 ` burnus at gcc dot gnu.org
2011-01-28 9:43 ` zazzou at gmail dot com
2011-01-28 10:19 ` burnus at gcc dot gnu.org
2011-01-29 22:23 ` zazzou at gmail dot com
2011-02-02 17:59 ` dnovillo at gcc dot gnu.org [this message]
2010-02-14 13:29 [Bug fortran/43062] New: " zazzou at gmail dot com
2010-02-14 17:21 ` [Bug fortran/43062] " pault at gcc dot gnu dot org
2010-02-14 17:27 ` kargl at gcc dot gnu dot org
2010-02-15 1:30 ` kargl at gcc dot gnu dot org
2010-02-15 8:18 ` zazzou at gmail dot com
2010-02-15 17:04 ` kargl at gcc dot gnu dot org
2010-02-15 20:34 ` jvdelisle at gcc dot gnu dot org
2010-02-15 21:47 ` kargl at gcc dot gnu dot org
2010-02-15 21:50 ` kargl at gcc dot gnu dot org
2010-02-17 2:07 ` jvdelisle at gcc dot gnu dot org
2010-02-17 7:32 ` burnus at gcc dot gnu dot org
2010-02-17 8:23 ` burnus at gcc dot gnu dot org
2010-02-17 15:57 ` kargl at gcc dot gnu dot org
2010-02-17 16:03 ` kargl at gcc dot gnu dot org
2010-02-17 21:26 ` burnus at gcc dot gnu dot org
2010-03-01 8:45 ` burnus at gcc dot gnu dot org
2010-04-06 18:42 ` burnus 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=bug-43062-4-bpsKiE0R8E@http.gcc.gnu.org/bugzilla/ \
--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).