From: Mikael Morin <mikael@gcc.gnu.org>
To: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: [PATCH 07/10] fortran: Support clobbering of ASSOCIATE variables [PR87397]
Date: Fri, 16 Sep 2022 22:24:36 +0200 [thread overview]
Message-ID: <20220916202439.549820-8-mikael@gcc.gnu.org> (raw)
In-Reply-To: <20220916202439.549820-1-mikael@gcc.gnu.org>
This is in spirit a revert of:
r9-3051-gc109362313623d83fe0a5194bceaf994cf0c6ce0
That commit added a condition to avoid generating ICE with clobbers
of ASSOCIATE variables.
The test added at that point continues to pass if we remove that
condition now.
PR fortran/87397
PR fortran/41453
gcc/fortran/ChangeLog:
* trans-expr.cc (gfc_conv_procedure_call): Remove condition
disabling clobber generation for ASSOCIATE variables.
---
gcc/fortran/trans-expr.cc | 1 -
1 file changed, 1 deletion(-)
diff --git a/gcc/fortran/trans-expr.cc b/gcc/fortran/trans-expr.cc
index d169df44a71..4491465c4d6 100644
--- a/gcc/fortran/trans-expr.cc
+++ b/gcc/fortran/trans-expr.cc
@@ -6527,7 +6527,6 @@ gfc_conv_procedure_call (gfc_se * se, gfc_symbol * sym,
&& !e->symtree->n.sym->attr.dimension
&& !e->symtree->n.sym->attr.pointer
&& !e->symtree->n.sym->attr.allocatable
- && !e->symtree->n.sym->attr.associate_var
&& e->ts.type != BT_CHARACTER
&& e->ts.type != BT_DERIVED
&& e->ts.type != BT_CLASS
--
2.35.1
next prev parent reply other threads:[~2022-09-16 20:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 20:24 [PATCH 00/10] fortran: clobber fixes [PR41453] Mikael Morin
2022-09-16 20:24 ` [PATCH 01/10] fortran: Move the clobber generation code Mikael Morin
2022-09-16 20:24 ` [PATCH 02/10] fortran: Fix invalid function decl clobber ICE [PR105012] Mikael Morin
2022-09-16 20:24 ` [PATCH 03/10] fortran: Move clobbers after evaluation of all arguments [PR106817] Mikael Morin
2022-09-16 20:24 ` [PATCH 04/10] fortran: Support clobbering with implicit interfaces [PR105012] Mikael Morin
2022-09-16 20:24 ` [PATCH 05/10] fortran: Support clobbering of reference variables [PR41453] Mikael Morin
2022-09-16 20:24 ` [PATCH 06/10] fortran: Support clobbering of SAVE variables [PR87395] Mikael Morin
2022-09-16 20:24 ` Mikael Morin [this message]
2022-09-16 20:24 ` [PATCH 08/10] fortran: Support clobbering of allocatables and pointers [PR41453] Mikael Morin
2022-09-16 20:24 ` [PATCH 09/10] fortran: Support clobbering of variable subreferences [PR88364] Mikael Morin
2022-09-17 17:03 ` Thomas Koenig
2022-09-17 19:33 ` Mikael Morin
2022-09-17 19:49 ` Bernhard Reutner-Fischer
2022-09-17 19:50 ` Mikael Morin
2022-09-17 21:24 ` Bernhard Reutner-Fischer
2022-09-18 6:12 ` Richard Biener
2022-09-18 9:10 ` Mikael Morin
2022-09-18 10:23 ` Thomas Koenig
2022-09-18 18:32 ` Harald Anlauf
2022-09-18 20:55 ` Mikael Morin
2022-09-19 7:11 ` Mikael Morin
2022-09-19 19:46 ` Harald Anlauf
2022-09-19 20:50 ` Mikael Morin
2022-09-20 6:54 ` Thomas Koenig
2022-09-20 8:46 ` Mikael Morin
2022-09-20 21:08 ` Harald Anlauf
2022-09-20 21:08 ` Harald Anlauf
2022-09-21 9:57 ` Thomas Koenig
2022-09-21 18:56 ` Mikael Morin
2022-09-21 19:12 ` Harald Anlauf
2022-09-21 19:12 ` Harald Anlauf
2022-09-18 20:43 ` Mikael Morin
2022-09-18 10:48 ` Richard Biener
2022-09-19 7:31 ` Mikael Morin
2022-09-19 7:58 ` Richard Biener
2022-09-16 20:24 ` [PATCH 10/10] fortran: Support clobbering of derived types [PR41453] Mikael Morin
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=20220916202439.549820-8-mikael@gcc.gnu.org \
--to=mikael@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).