public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33542] gfortran does not detect ambigious specific names if they are the same as generic names
Date: Fri, 12 Oct 2007 16:52:00 -0000 [thread overview]
Message-ID: <20071012165204.3016.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33542-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from pault at gcc dot gnu dot org 2007-10-12 16:52 -------
Subject: Bug 33542
Author: pault
Date: Fri Oct 12 16:51:53 2007
New Revision: 129268
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129268
Log:
2007-10-12 Paul Thomas <pault@gcc.gnu.org>
PR fortran/33542
* resolve.c (resolve_actual_arglist): If the actual argument is
ambiguous, then there is an error.
2007-10-12 Paul Thomas <pault@gcc.gnu.org>
PR fortran/33542
* gfortran.dg/ambiguous_specific_1.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/ambiguous_specific_1.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33542
next prev parent reply other threads:[~2007-10-12 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 9:06 [Bug fortran/33542] New: " burnus at gcc dot gnu dot org
2007-09-24 20:55 ` [Bug fortran/33542] " burnus at gcc dot gnu dot org
2007-09-30 16:53 ` pault at gcc dot gnu dot org
2007-10-02 10:05 ` dominiq at lps dot ens dot fr
2007-10-02 11:45 ` pault at gcc dot gnu dot org
2007-10-02 11:47 ` pault at gcc dot gnu dot org
2007-10-04 4:46 ` pault at gcc dot gnu dot org
2007-10-04 4:49 ` pault at gcc dot gnu dot org
2007-10-07 19:05 ` patchapp at dberlin dot org
2007-10-12 16:52 ` pault at gcc dot gnu dot org [this message]
2007-10-14 19:27 ` pault 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=20071012165204.3016.qmail@sourceware.org \
--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).