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/103474] ICE in simplify_cobound, at fortran/simplify.c:4415
Date: Wed, 26 Oct 2022 20:44:50 +0000	[thread overview]
Message-ID: <bug-103474-4-5vgnVAc62E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103474-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from anlauf at gcc dot gnu.org ---
I am now stuck with the following code, which I believe is valid.
(It is accepted by Crayftn and rejected by Intel, but I thought it is
covered by F2018:5.4.7(5)):

program p
  type t
     integer :: a(1,2)
  end type
  class(t), allocatable :: x[:]
  print *, ucobound (x%a)
end

The problem I have is that gfc_conv_expr_descriptor invokes walk_coarray,
but the result depends on the rank of the array a in type t.
The comment before walk_coarray states:

/* Convert the last ref of a scalar coarray from an AR_ELEMENT to an
   AR_FULL, suitable for the scalarizer.  */

However, we should find a way to only extract the "co-descriptor".
We might also need that when implement COSHAPE.

      parent reply	other threads:[~2022-10-26 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 18:51 [Bug fortran/103474] New: " gscfq@t-online.de
2021-11-29 20:40 ` [Bug fortran/103474] " kargl at gcc dot gnu.org
2022-01-26 17:24 ` gscfq@t-online.de
2022-10-20 21:01 ` anlauf at gcc dot gnu.org
2022-10-25 19:27 ` anlauf at gcc dot gnu.org
2022-10-26 20:44 ` anlauf at gcc dot gnu.org [this message]

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-103474-4-5vgnVAc62E@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).