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/103716] [10/11/12/13/14 Regression] ICE in gimplify_expr, at gimplify.c:15964 since r9-3803-ga5fbc2f36a291cbe
Date: Tue, 23 May 2023 05:46:47 +0000 [thread overview]
Message-ID: <bug-103716-4-K6Etg0kfsI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103716-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103716
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Paul Thomas <pault@gcc.gnu.org>:
https://gcc.gnu.org/g:842a432b02238361ecc601d301ac400a7f30f4fa
commit r14-1082-g842a432b02238361ecc601d301ac400a7f30f4fa
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Tue May 23 06:46:37 2023 +0100
Fortran: Fix assumed length chars and len inquiry [PR103716]
2023-05-23 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran
PR fortran/103716
* resolve.cc (gfc_resolve_ref): Conversion of array_ref into an
element should be done for all characters without a len expr,
not just deferred lens, and for integer expressions.
* trans-expr.cc (conv_inquiry): For len and kind inquiry refs,
set the se string_length to NULL_TREE.
gcc/testsuite/
PR fortran/103716
* gfortran.dg/pr103716.f90 : New test.
next prev parent reply other threads:[~2023-05-23 5:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 18:11 [Bug fortran/103716] New: [10/11/12 Regression] ICE in gimplify_expr, at gimplify.c:15964 gscfq@t-online.de
2021-12-15 11:16 ` [Bug fortran/103716] [10/11/12 Regression] ICE in gimplify_expr, at gimplify.c:15964 since r9-3803-ga5fbc2f36a291cbe marxin at gcc dot gnu.org
2021-12-15 19:56 ` anlauf at gcc dot gnu.org
2021-12-16 8:57 ` gscfq@t-online.de
2021-12-16 17:23 ` anlauf at gcc dot gnu.org
2021-12-16 21:32 ` anlauf at gcc dot gnu.org
2022-01-04 11:14 ` rguenth at gcc dot gnu.org
2022-01-17 12:44 ` rguenth at gcc dot gnu.org
2022-06-28 10:47 ` [Bug fortran/103716] [10/11/12/13 " jakub at gcc dot gnu.org
2023-05-23 5:46 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-07 10:41 ` [Bug fortran/103716] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-08 19:08 ` [Bug fortran/103716] [11/12/13 " anlauf at gcc dot gnu.org
2024-03-28 15:53 ` cvs-commit at gcc dot gnu.org
2024-03-28 15:56 ` pault at gcc dot gnu.org
2024-04-26 19:16 ` cvs-commit 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-103716-4-K6Etg0kfsI@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).