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/54199] Superfluous diagnostic "is also the name of an intrinsic" for internal procedures
Date: Thu, 09 Aug 2012 12:07:00 -0000 [thread overview]
Message-ID: <bug-54199-4-hnI9zaDWyi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54199-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54199
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-08-09 12:06:36 UTC ---
Author: burnus
Date: Thu Aug 9 12:06:31 2012
New Revision: 190251
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190251
Log:
2012-08-09 Tobias Burnus <burnus@net-b.de>
PR fortran/54199
* intrinsic.c (gfc_warn_intrinsic_shadow): Better warning
for internal procedures.
2012-08-09 Tobias Burnus <burnus@net-b.de>
PR fortran/54199
* gfortran.dg/intrinsic_shadow_4.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/intrinsic_shadow_4.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/intrinsic.c
trunk/gcc/testsuite/ChangeLog
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-08-09 12:06:57 UTC ---
FIXED on the 4.8 trunk.
prev parent reply other threads:[~2012-08-09 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 10:46 [Bug fortran/54199] New: " burnus at gcc dot gnu.org
2012-08-08 19:55 ` [Bug fortran/54199] " mikael at gcc dot gnu.org
2012-08-09 7:52 ` burnus at gcc dot gnu.org
2012-08-09 12:07 ` burnus at gcc dot gnu.org
2012-08-09 12:07 ` burnus at gcc dot gnu.org
2012-08-09 12:07 ` burnus at gcc dot gnu.org [this message]
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-54199-4-hnI9zaDWyi@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).