public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104908] [11/12/13/14 Regression] incorrect Fortran out-of-bound runtime error.
Date: Fri, 26 Jan 2024 20:20:37 +0000	[thread overview]
Message-ID: <bug-104908-4-mUXEUcsoer@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104908-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104908

--- Comment #6 from anlauf at gcc dot gnu.org ---
Studying the cases that ICE (CLASS array dummy) and testcase PR95331.f90
which fixes an unlimited polymorphic problem, I tried the following change:

diff --git a/gcc/fortran/trans-array.cc b/gcc/fortran/trans-array.cc
index f6ddce2d023..be7d42ff847 100644
--- a/gcc/fortran/trans-array.cc
+++ b/gcc/fortran/trans-array.cc
@@ -4097,7 +4097,10 @@ gfc_conv_array_ref (gfc_se * se, gfc_array_ref * ar,
gfc_expr *expr,
     }

   decl = se->expr;
-  if (IS_CLASS_ARRAY (sym) && sym->attr.dummy && ar->as->type != AS_DEFERRED)
+  if (UNLIMITED_POLY(sym)
+      && IS_CLASS_ARRAY (sym)
+      && sym->attr.dummy
+      && ar->as->type != AS_DEFERRED)
     decl = sym->backend_decl;

   cst_offset = offset = gfc_index_zero_node;


This is currently regtesting.

  parent reply	other threads:[~2024-01-26 20:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13 21:58 [Bug fortran/104908] New: gfortran 11/trunk regression: " a.shahmoradi at gmail dot com
2022-03-15 20:49 ` [Bug fortran/104908] [11/12 Regression] " anlauf at gcc dot gnu.org
2022-03-17 22:23 ` anlauf at gcc dot gnu.org
2022-03-22 10:33 ` rguenth at gcc dot gnu.org
2022-04-21  7:51 ` rguenth at gcc dot gnu.org
2023-05-29 10:06 ` [Bug fortran/104908] [11/12/13/14 " jakub at gcc dot gnu.org
2024-01-24 18:41 ` anlauf at gcc dot gnu.org
2024-01-26 20:20 ` anlauf at gcc dot gnu.org [this message]
2024-01-26 21:01 ` anlauf at gcc dot gnu.org
2024-01-27  0:25 ` jvdelisle at gcc dot gnu.org
2024-01-27 16:52 ` cvs-commit at gcc dot gnu.org
2024-01-31 19:28 ` cvs-commit at gcc dot gnu.org
2024-02-09 20:28 ` cvs-commit at gcc dot gnu.org
2024-02-09 20:28 ` cvs-commit at gcc dot gnu.org
2024-02-09 20:30 ` anlauf at gcc dot gnu.org
2024-03-07 21:06 ` 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-104908-4-mUXEUcsoer@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).