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/94331] Bind(C) corrupts array descriptors
Date: Fri, 14 May 2021 03:04:12 +0000	[thread overview]
Message-ID: <bug-94331-4-Y0ecCqhiAA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94331-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from sandra at gcc dot gnu.org ---
OK, there are two flavors of failures being diagnosed by the test case.

The first flavor involves the lower bounds of an array passed into a bind(c)
procedure being set to zero in the callee when the test case thinks they should
be inherited from the array in the caller.  I'm still trying to grok what the
standard actually says about these cases.

The second flavor looks like the same bug as PR93308, involving the lower
bounds of an array passed to a bind(c) procedure appearing to be correct in the
callee, but set to zero in the caller after return.

  parent reply	other threads:[~2021-05-14  3:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 15:52 [Bug fortran/94331] New: " jrfsousa at gmail dot com
2020-03-25 15:52 ` [Bug fortran/94331] " jrfsousa at gmail dot com
2020-07-23 20:08 ` dominiq at lps dot ens.fr
2021-05-12  3:15 ` sandra at gcc dot gnu.org
2021-05-14  3:04 ` sandra at gcc dot gnu.org [this message]
2021-05-14 16:16 ` jrfsousa at gcc dot gnu.org
2021-05-19 18:09 ` jrfsousa at gcc dot gnu.org
2021-05-30 17:04 ` dominiq at lps dot ens.fr
2021-05-30 17:12 ` dominiq at lps dot ens.fr
2021-05-30 20:17 ` jrfsousa at gcc dot gnu.org
2021-05-30 20:18 ` jrfsousa at gcc dot gnu.org
2021-05-30 20:48 ` dominiq at lps dot ens.fr
2021-06-14 23:14 ` jrfsousa at gcc dot gnu.org
2021-06-14 23:22 ` jrfsousa at gcc dot gnu.org
2021-07-26 12:33 ` cvs-commit at gcc dot gnu.org
2021-10-19 10:20 ` burnus 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-94331-4-Y0ecCqhiAA@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).