public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104649] ICE in gfc_match_formal_arglist, at fortran/decl.cc:6733 since r6-1958-g4668d6f9c00d4767
Date: Sun, 09 Jul 2023 17:59:04 +0000 [thread overview]
Message-ID: <bug-104649-4-09M2APgZD8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104649-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104649
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to kargl from comment #2)
> Null pointer dereference.
>
>
> diff --git a/gcc/fortran/decl.cc b/gcc/fortran/decl.cc
> index bd586e75008..8e2cd511c4d 100644
> --- a/gcc/fortran/decl.cc
> +++ b/gcc/fortran/decl.cc
> @@ -6730,12 +6730,20 @@ ok:
> || (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)
> + || (p->sym && q->sym
> + && 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 (q->sym)
> + gfc_error_now ("Mismatch in MODULE PROCEDURE formal "
> + "argument names (%qs/%qs) at %C",
> + p->sym->name, q->sym->name);
> + else
> + gfc_error_now ("Mismatch in MODULE PROCEDURE formal argument "
> + "name, %qs, and alternate return at %C",
> + p->sym->name);
> + }
> }
>
> if (arg_count_mismatch)
The second testcase still segfaults and everything is so optimised away that I
cannot figure out why.
Paul
next prev parent reply other threads:[~2023-07-09 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 19:34 [Bug fortran/104649] New: ICE in gfc_match_formal_arglist, at fortran/decl.cc:6733 gscfq@t-online.de
2022-02-24 15:31 ` [Bug fortran/104649] ICE in gfc_match_formal_arglist, at fortran/decl.cc:6733 since r6-1958-g4668d6f9c00d4767 marxin at gcc dot gnu.org
2022-05-17 17:44 ` kargl at gcc dot gnu.org
2023-07-09 17:59 ` pault at gcc dot gnu.org [this message]
2023-10-24 20:16 ` anlauf at gcc dot gnu.org
2023-10-26 20:44 ` anlauf at gcc dot gnu.org
2023-10-27 17:18 ` cvs-commit at gcc dot gnu.org
2023-10-27 17:50 ` sgk at troutmask dot apl.washington.edu
2023-10-27 18:51 ` anlauf 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-104649-4-09M2APgZD8@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).