public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107266] Reject kind=4 characters for BIND(C) – it invalid and generates wrong code
Date: Mon, 17 Oct 2022 16:56:57 +0000	[thread overview]
Message-ID: <bug-107266-4-1ajezpyKc1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107266-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from kargl at gcc dot gnu.org ---
(In reply to CVS Commits from comment #8)
> The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:
> 
> https://gcc.gnu.org/g:8950288333162caa68b85c71ed2d02f40976ddb9
> 
> commit r13-3338-g8950288333162caa68b85c71ed2d02f40976ddb9
> Author: Tobias Burnus <tobias@codesourcery.com>
> Date:   Mon Oct 17 18:15:16 2022 +0200
> 
>     Fortran: Fixes for kind=4 characters strings [PR107266]
>     
>             PR fortran/107266
>     
>     gcc/fortran/
>             * trans-expr.cc (gfc_conv_string_parameter): Use passed
>             type to honor character kind.
>             * trans-types.cc (gfc_sym_type): Honor character kind.
>             * trans-decl.cc (gfc_conv_cfi_to_gfc): Fix handling kind=4
>             character strings.
>     
>     gcc/testsuite/
>             * gfortran.dg/char4_decl.f90: New test.
>             * gfortran.dg/char4_decl-2.f90: New test.

Please commit the patch in comment #7.  character(kind=4) is not interoperable
(unless C_CHAR is CHARACTER(KIND=4) which it isn't).  This is an extension and
gfortran should flag.

  parent reply	other threads:[~2022-10-17 16:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 16:04 [Bug fortran/107266] New: " burnus at gcc dot gnu.org
2022-10-14 16:09 ` [Bug fortran/107266] " burnus at gcc dot gnu.org
2022-10-14 18:31 ` kargl at gcc dot gnu.org
2022-10-14 18:51 ` kargl at gcc dot gnu.org
2022-10-14 18:51 ` kargl at gcc dot gnu.org
2022-10-14 20:08 ` kargl at gcc dot gnu.org
2022-10-14 21:36 ` burnus at gcc dot gnu.org
2022-10-14 22:21 ` sgk at troutmask dot apl.washington.edu
2022-10-14 22:45 ` kargl at gcc dot gnu.org
2022-10-17 16:15 ` cvs-commit at gcc dot gnu.org
2022-10-17 16:56 ` kargl at gcc dot gnu.org [this message]
2022-10-18 10:40 ` burnus at gcc dot gnu.org
2022-10-18 17:29 ` sgk at troutmask dot apl.washington.edu
2022-10-18 22:43 ` sgk at troutmask dot apl.washington.edu
2022-10-18 23:18 ` sgk at troutmask dot apl.washington.edu

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-107266-4-1ajezpyKc1@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).