public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58331] [OOP] Bogus rank checking with explicit-/assumed-size arrays and CLASS
Date: Wed, 15 Mar 2023 08:58:41 +0000	[thread overview]
Message-ID: <bug-58331-4-oENyLe6x5A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58331-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> ---
COARRAYS:

(In reply to anlauf from comment #7)
> I tried other testcases that use coarrays, but e.g. the following scalar
> coarray case produces an ICE later on.  I believe this is a pre-existing
> separate issue.

A coarray 'ca' can either be a local variable (the usual case), a remove
reference (then with '[indx]' in the expr) - or, like here, the full thing.

In gfc_conv_intrinsic_to_class, the gfc_conv_expr_reference 'destroys' the
coarray part. I think we need something like 'gfc_conv_variable' — and I bet
that we need to ensure all combinations work:

(scalar,array w/o and w/ descriptor) → (assumed rank, array w/o and w/
descriptor) - where the 'to class' (and, obviously, the 'from' was well) are
coarrays.

Besides intrinsic types -> class(*), we should also check check
type(t) -> ('class(t)' and 'class(*)')

  parent reply	other threads:[~2023-03-15  8:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06  6:00 [Bug fortran/58331] New: " burnus at gcc dot gnu.org
2013-09-06 21:35 ` [Bug fortran/58331] " burnus at gcc dot gnu.org
2013-09-08 16:46 ` burnus at gcc dot gnu.org
2014-03-22 15:02 ` dominiq at lps dot ens.fr
2023-03-06 21:43 ` anlauf at gcc dot gnu.org
2023-03-06 22:13 ` anlauf at gcc dot gnu.org
2023-03-07  9:14 ` burnus at gcc dot gnu.org
2023-03-09 19:44 ` anlauf at gcc dot gnu.org
2023-03-14 19:39 ` anlauf at gcc dot gnu.org
2023-03-15  8:58 ` burnus at gcc dot gnu.org [this message]
2023-03-15 19:22 ` cvs-commit at gcc dot gnu.org
2023-03-15 20:03 ` 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-58331-4-oENyLe6x5A@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).