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 libfortran/101310] New: Bind(C): CFI_section seems confused by pointer arrays
Date: Sat, 03 Jul 2021 20:48:57 +0000	[thread overview]
Message-ID: <bug-101310-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101310
           Summary: Bind(C): CFI_section seems confused by pointer arrays
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libfortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sandra at gcc dot gnu.org
  Target Milestone: ---

Many of the unit tests for CFI_section included in the WIP TS 29113 testsuite
are failing.

https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574115.html

At least some of the problems seem to be related to handling pointer arrays
where the lower bound may be nonzero; e.g. section-1p and section-2p fail, but
the corresponding non-pointer cases sharing the same C code pass.

The set of tests that seem affected by this bug are:

library/section-1p.f90
library/section-2p.f90
library/section-3.f90
library/section-3p.f90

and also

interoperability/fc-out-descriptor-7.f90

which tries to pass the result of CFI_section back to Fortran via an
intent(out) argument (the unit tests only manipulate it in C code).

             reply	other threads:[~2021-07-03 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 20:48 sandra at gcc dot gnu.org [this message]
2021-07-17 20:35 ` [Bug libfortran/101310] " sandra at gcc dot gnu.org
2021-07-18  5:54 ` sandra at gcc dot gnu.org
2021-07-28  4:25 ` cvs-commit at gcc dot gnu.org
2021-07-28 20:22 ` sandra 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-101310-4@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).