public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ivan.tubert-brohman at schrodinger dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92482] BIND(C) with array-descriptor mishandled for type character
Date: Thu, 29 Apr 2021 16:09:29 +0000	[thread overview]
Message-ID: <bug-92482-4-3GKK3UAtcJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92482-4@http.gcc.gnu.org/bugzilla/>

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

Ivan Tubert-Brohman <ivan.tubert-brohman at schrodinger dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ivan.tubert-brohman@schrodi
                   |                            |nger.com

--- Comment #3 from Ivan Tubert-Brohman <ivan.tubert-brohman at schrodinger dot com> ---
I also encountered this issue. I was trying the example given by Metcalf et al.
on _Modern Fortran Explained_ (2018), section 21.4, "Assumed character length":

      interface
         subroutine err_msg(string) bind(c)
            use iso_c_binding
            character(*, c_char), intent(in):: string
         end subroutine err_msg
      end interface

The example worked with the Intel Fortran compiler, but with gfortran 11.1 I
get

  Error: Character argument ‘string’ at (1) must be length 1 because procedure
‘err_msg’ is BIND(C)

I only comment to confirm that both a famous author and an alternative compiler
implementation agree with the interpretation of the standard that this should
work. :-)

       reply	other threads:[~2021-04-29 16:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92482-4@http.gcc.gnu.org/bugzilla/>
2021-04-29 16:09 ` ivan.tubert-brohman at schrodinger dot com [this message]
2021-07-25 17:10 ` sandra at gcc dot gnu.org
2021-07-27 10:23 ` burnus at gcc dot gnu.org
2021-08-31 10:52 ` burnus at gcc dot gnu.org
2021-10-18  8:29 ` cvs-commit at gcc dot gnu.org
2021-10-19 10:37 ` burnus at gcc dot gnu.org
2021-10-19 13:17 ` cvs-commit at gcc dot gnu.org
2021-10-19 13:20 ` burnus at gcc dot gnu.org
2021-10-22 20:42 ` 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-92482-4-3GKK3UAtcJ@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).