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/100154] [9/10/11/12 Regression] ICE in gfc_conv_procedure_call, at fortran/trans-expr.c:6131
Date: Tue, 27 Apr 2021 21:41:20 +0000 [thread overview]
Message-ID: <bug-100154-4-C1zJ4OvBd3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100154-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100154
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:21992a791aded6d818da39079546c067f3362e8b
commit r9-9469-g21992a791aded6d818da39079546c067f3362e8b
Author: Harald Anlauf <anlauf@gmx.de>
Date: Sat Apr 24 20:51:41 2021 +0200
PR fortran/100154 - ICE in gfc_conv_procedure_call, at
fortran/trans-expr.c:6131
Add appropriate static checks for the character and status arguments to
the GNU Fortran intrinsic extensions fget[c], fput[c]. Extend variable
check to allow a function reference having a data pointer result.
gcc/fortran/ChangeLog:
PR fortran/100154
* check.c (variable_check): Allow function reference having a data
pointer result.
(arg_strlen_is_zero): New function.
(gfc_check_fgetputc_sub): Add static check of character and status
arguments.
(gfc_check_fgetput_sub): Likewise.
* intrinsic.c (add_subroutines): Fix argument name for the
character argument to intrinsic subroutines fget[c], fput[c].
gcc/testsuite/ChangeLog:
PR fortran/100154
* gfortran.dg/pr100154.f90: New test.
(cherry picked from commit d0e7833b94953ba6b4a915150666969ad9fc66af)
next prev parent reply other threads:[~2021-04-27 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 17:36 [Bug fortran/100154] New: [9/10/11 " gscfq@t-online.de
2021-04-20 20:58 ` [Bug fortran/100154] " anlauf at gcc dot gnu.org
2021-04-20 21:21 ` anlauf at gcc dot gnu.org
2021-04-21 6:19 ` marxin at gcc dot gnu.org
2021-04-21 8:51 ` burnus at gcc dot gnu.org
2021-04-21 20:00 ` [Bug fortran/100154] [9/10/11/12 " anlauf at gcc dot gnu.org
2021-04-21 20:09 ` anlauf at gcc dot gnu.org
2021-04-21 20:36 ` anlauf at gcc dot gnu.org
2021-04-21 20:55 ` anlauf at gcc dot gnu.org
2021-04-22 21:06 ` anlauf at gcc dot gnu.org
2021-04-24 18:52 ` cvs-commit at gcc dot gnu.org
2021-04-24 19:48 ` anlauf at gcc dot gnu.org
2021-04-27 21:13 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:29 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:41 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-27 21:42 ` 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-100154-4-C1zJ4OvBd3@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).