public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52101] Obsolescence warning for non-obs. feature character name*length
Date: Tue, 17 Jul 2012 09:40:00 -0000 [thread overview]
Message-ID: <bug-52101-4-8wXJX3FqxP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52101-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52101
--- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-07-17 09:40:18 UTC ---
Author: burnus
Date: Tue Jul 17 09:40:12 2012
New Revision: 189565
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=189565
Log:
2012-07-17 Tobias Burnus <burnus@net-b.de>
PR fortran/52101
* decl.c (match_char_length): Extra argument, show obsolenscent
warning only if *length is used after the typename.
(variable_decl, gfc_match_char_spec): Update call
2012-07-17 Tobias Burnus <burnus@net-b.de>
PR fortran/52101
* gfortran.dg/oldstyle_4.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/oldstyle_4.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/decl.c
trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-07-17 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 0:11 [Bug fortran/52101] New: " john.harper at vuw dot ac.nz
2012-02-03 7:22 ` [Bug fortran/52101] " burnus at gcc dot gnu.org
2012-02-03 7:31 ` burnus at gcc dot gnu.org
2012-02-03 20:51 ` John.Harper at msor dot vuw.ac.nz
2012-02-03 21:17 ` kargl at gcc dot gnu.org
2012-02-03 22:48 ` sgk at troutmask dot apl.washington.edu
2012-02-04 0:01 ` sgk at troutmask dot apl.washington.edu
2012-02-05 9:59 ` burnus at gcc dot gnu.org
2012-02-05 18:01 ` sgk at troutmask dot apl.washington.edu
2012-02-05 18:12 ` burnus at gcc dot gnu.org
2012-07-16 19:38 ` burnus at gcc dot gnu.org
2012-07-17 9:40 ` burnus at gcc dot gnu.org [this message]
2012-07-17 11:28 ` 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=bug-52101-4-8wXJX3FqxP@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).