public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103287] [12 Regression] ICE in argument_rank_mismatch, at fortran/interface.c:2240
Date: Thu, 06 Jan 2022 20:46:23 +0000 [thread overview]
Message-ID: <bug-103287-4-ppFhCLvy0S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103287-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103287
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>:
https://gcc.gnu.org/g:8e2771069ed0c157cca825d6af5792e94c4407c1
commit r12-6322-g8e2771069ed0c157cca825d6af5792e94c4407c1
Author: Sandra Loosemore <sandra@codesourcery.com>
Date: Wed Jan 5 13:18:10 2022 -0800
Fortran: Fix ICE in argument_rank_mismatch [PR103287]
This patch removes an incorrect assertion. A user-friendly error for this
case is already given elsewhere.
2022-01-05 Steve Kargl <kargl@gcc.gnu.org>
Sandra Loosemore <sandra@codesourcery.com>
PR fortran/103287
gcc/fortran/
* interface.c (argument_rank_mismatch): Replace incorrect assertion
with return.
gcc/testsuite/
* gfortran.dg/c-interop/pr103287-1.f90: new.
* gfortran.dg/c-interop/pr103287-2.f90: new.
next prev parent reply other threads:[~2022-01-06 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 18:41 [Bug fortran/103287] New: " gscfq@t-online.de
2021-11-16 18:42 ` [Bug fortran/103287] " gscfq@t-online.de
2021-11-16 20:05 ` kargl at gcc dot gnu.org
2021-11-16 20:08 ` kargl at gcc dot gnu.org
2021-11-18 7:40 ` rguenth at gcc dot gnu.org
2021-11-18 10:35 ` marxin at gcc dot gnu.org
2021-12-13 1:48 ` sandra at gcc dot gnu.org
2021-12-13 2:11 ` kargl at gcc dot gnu.org
2022-01-06 20:46 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-06 20:47 ` sandra at gcc dot gnu.org
2022-09-16 20:12 ` anlauf at gcc dot gnu.org
2022-09-16 20:12 ` 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-103287-4-ppFhCLvy0S@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).