From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR68534 - No error on mismatch in number of arguments between submodule and module interface
Date: Thu, 03 Dec 2015 06:43:00 -0000 [thread overview]
Message-ID: <20151203064341.GA62254@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20151203062630.GA62157@troutmask.apl.washington.edu>
On Wed, Dec 02, 2015 at 10:26:30PM -0800, Steve Kargl wrote:
> On Wed, Dec 02, 2015 at 10:02:33PM -0800, Steve Kargl wrote:
> > Paul,
> >
> > I'm stumped. Something is broken on i386-*-freebsd. :-(
> >
> > Running /mnt/kargl/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
> > FAIL: gfortran.dg/submodule_10.f08 -O (internal compiler error)
> > FAIL: gfortran.dg/submodule_10.f08 -O (test for excess errors)
> > FAIL: gfortran.dg/submodule_11.f08 -O0 (internal compiler error)
> > FAIL: gfortran.dg/submodule_11.f08 -O0 (test for excess errors)
> > FAIL: gfortran.dg/submodule_11.f08 -O1 (internal compiler error)
> > FAIL: gfortran.dg/submodule_11.f08 -O1 (test for excess errors)
> > FAIL: gfortran.dg/submodule_11.f08 -O2 (internal compiler error)
> > FAIL: gfortran.dg/submodule_11.f08 -O2 (test for excess errors)
> > FAIL: gfortran.dg/submodule_11.f08 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error)
> > FAIL: gfortran.dg/submodule_11.f08 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
> > FAIL: gfortran.dg/submodule_11.f08 -O3 -g (internal compiler error)
> > FAIL: gfortran.dg/submodule_11.f08 -O3 -g (test for excess errors)
> > FAIL: gfortran.dg/submodule_11.f08 -Os (internal compiler error)
> > FAIL: gfortran.dg/submodule_11.f08 -Os (test for excess errors)
>
> Well, if I change the order of the conditionals decl.c:4831, I
> can get rid of the above FAILs.
>
> Index: decl.c
> ===================================================================
> --- decl.c (revision 231219)
> +++ decl.c (working copy)
> @@ -4826,7 +4826,7 @@ ok:
>
> /* Abbreviated module procedure declaration is not meant to have any
> formal arguments! */
> - if (!sym->abr_modproc_decl && formal && !head)
> + if (formal && !head && sym && !sym->abr_modproc_decl)
> arg_count_mismatch = true;
>
> for (p = formal, q = head; p && q; p = p->next, q = q->next)
>
> --
> steve
>
> > FAIL: gfortran.dg/submodule_13.f08 -O (internal compiler error)
> > FAIL: gfortran.dg/submodule_13.f08 -O (test for errors, line 29)
> > FAIL: gfortran.dg/submodule_13.f08 -O (test for excess errors)
These ICEs persist at line 4831. In looking at the code, I'm
now somewhat unsure what it should be doing. In particular,
there are 2 gfc_error_now() calls in the below:
for (p = formal, q = head; p && q; p = p->next, q = q->next)
{
if ((p->next != NULL && q->next == NULL)
|| (p->next == NULL && q->next != NULL))
arg_count_mismatch = true;
else if ((p->sym == NULL && q->sym == NULL)
|| strcmp (p->sym->name, q->sym->name) == 0)
continue;
else
gfc_error_now ("Mismatch in MODULE PROCEDURE formal "
"argument names (%s/%s) at %C",
p->sym->name, q->sym->name);
}
if (arg_count_mismatch)
gfc_error_now ("Mismatch in number of MODULE PROCEDURE "
"formal arguments at %C");
}
return MATCH_YES;
cleanup:
gfc_free_formal_arglist (head);
return m;
But, we return MATCH_YES? I would expect setting m = MATCH_ERROR
and jumping to cleanup. That's ugly.
--
Steve
next prev parent reply other threads:[~2015-12-03 6:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 10:35 Paul Richard Thomas
2015-11-28 16:19 ` Steve Kargl
2015-11-30 13:35 ` Paul Richard Thomas
2015-12-03 6:02 ` Steve Kargl
2015-12-03 6:26 ` Steve Kargl
2015-12-03 6:43 ` Steve Kargl [this message]
2015-12-03 11:31 ` Paul Richard Thomas
2015-12-05 15:20 ` Paul Richard Thomas
2015-12-05 16:07 ` Steve Kargl
2015-12-05 16:41 ` Steve Kargl
2015-12-05 17:25 ` Paul Richard Thomas
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=20151203064341.GA62254@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/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).