public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99256] ICE in variable_check, at fortran/check.c:1012 Date: Sun, 12 Dec 2021 21:47:05 +0000 [thread overview] Message-ID: <bug-99256-4-jCW08G9eI7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99256-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99256 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #3 from anlauf at gcc dot gnu.org --- We could get approximate locus info with e.g. diff --git a/gcc/fortran/intrinsic.c b/gcc/fortran/intrinsic.c index 3682f9ae21f..78dfdbe7c92 100644 --- a/gcc/fortran/intrinsic.c +++ b/gcc/fortran/intrinsic.c @@ -5108,6 +5108,15 @@ gfc_intrinsic_sub_interface (gfc_code *c, int error_flag) if (!do_ts29113_check (isym, c->ext.actual)) goto fail; + gfc_actual_arglist *actual; + for (actual = c->ext.actual; actual; actual = actual->next) + if (actual->label) + { + gfc_error ("Label %d not allowed as argument of intrinsic %qs at %L", + actual->label->value, name, &c->loc); + goto fail; + } + if (isym->check.f1 != NULL) { if (!do_check (isym, c->ext.actual)) which regtests ok.
next prev parent reply other threads:[~2021-12-12 21:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 17:31 [Bug fortran/99256] New: " gscfq@t-online.de 2021-02-25 18:40 ` [Bug fortran/99256] " kargl at gcc dot gnu.org 2021-02-25 18:49 ` sgk at troutmask dot apl.washington.edu 2021-12-12 21:47 ` anlauf at gcc dot gnu.org [this message] 2022-01-13 22:39 ` anlauf at gcc dot gnu.org 2022-01-13 23:08 ` kargl at gcc dot gnu.org 2022-01-14 20:48 ` cvs-commit at gcc dot gnu.org 2022-01-14 20:57 ` 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-99256-4-jCW08G9eI7@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: linkBe 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).