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/100103] Automatic reallocation fails inside select rank
Date: Sat, 01 Oct 2022 18:17:34 +0000 [thread overview]
Message-ID: <bug-100103-4-nXy71J8Hjc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100103-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100103
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:56275fd23e3f7876c24a812f9b6776b00a94744e
commit r12-8803-g56275fd23e3f7876c24a812f9b6776b00a94744e
Author: José Rui Faustino de Sousa <jrfsousa@gmail.com>
Date: Wed Sep 21 22:55:02 2022 +0200
Fortran: Fix automatic reallocation inside select rank [PR100103]
gcc/fortran/ChangeLog:
PR fortran/100103
* trans-array.cc (gfc_is_reallocatable_lhs): Add select rank
temporary associate names as possible targets of automatic
reallocation.
gcc/testsuite/ChangeLog:
PR fortran/100103
* gfortran.dg/PR100103.f90: New test.
(cherry picked from commit 12b537b9b7fd50f4b2fbfcb7ccf45f8d66085577)
next prev parent reply other threads:[~2022-10-01 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 16:33 [Bug fortran/100103] New: " jrfsousa at gmail dot com
2021-04-16 13:40 ` [Bug fortran/100103] " dominiq at lps dot ens.fr
2022-09-21 21:08 ` anlauf at gcc dot gnu.org
2022-09-22 17:40 ` cvs-commit at gcc dot gnu.org
2022-10-01 18:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-01 18:45 ` anlauf at gcc dot gnu.org
2022-10-29 20:25 ` anlauf at gcc dot gnu.org
2022-10-29 20:26 ` 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-100103-4-nXy71J8Hjc@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).