public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94070] Assumed-rank arrays – bounds mishandled, SIZE/SHAPE/UBOUND/LBOUND
Date: Thu, 01 Jul 2021 22:55:52 +0000 [thread overview]
Message-ID: <bug-94070-4-P7BsvofdgJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94070-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94070
sandra at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandra at gcc dot gnu.org
--- Comment #7 from sandra at gcc dot gnu.org ---
I think the remaining bind(c) problems are the same bug that is causing
failures in tests
interoperability/cf-out-descriptor-6.f90
interoperability/fc-descriptor-6.f90
interoperability/fc-out-descriptor-6.f90
interoperability/ff-descriptor-6.f90
intrinsics/size.f90
from the new TS29113 testsuite posted at
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574115.html
TS29113 says:
(1) for an assumed-rank object that is associated with an
assumed-size array, the result has the value −1 if DIM is
present and equal to the rank of ARRAY
Also in the description of CFI_cdesc_t in section 8.3.3, it says
In a C descriptor of an assumed-size array, the extent member of the
last element of the dim member has the value −1.
Neither of these things appears to be happening.
This might also be related to PR 94289?
next prev parent reply other threads:[~2021-07-01 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-94070-4@http.gcc.gnu.org/bugzilla/>
2020-07-21 15:22 ` dominiq at lps dot ens.fr
2021-03-01 8:34 ` burnus at gcc dot gnu.org
2021-07-01 22:55 ` sandra at gcc dot gnu.org [this message]
2021-08-22 19:53 ` sandra at gcc dot gnu.org
2021-09-06 11:56 ` burnus at gcc dot gnu.org
2021-09-27 12:06 ` cvs-commit at gcc dot gnu.org
2021-10-12 2:57 ` sandra at gcc dot gnu.org
2021-10-21 2:28 ` cvs-commit at gcc dot gnu.org
2021-10-21 18:03 ` sandra at gcc dot gnu.org
2022-01-09 23:25 ` pinskia 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-94070-4-P7BsvofdgJ@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).