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: Fri, 14 Oct 2022 18:51:22 +0000	[thread overview]
Message-ID: <bug-107266-4-buFjox8smI@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 #3 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #2)
> (In reply to Tobias Burnus from comment #1)
> > Better example:
> > 
> > character(kind=4) function f(x) bind(C)
> >   character(kind=4), value :: x
> > end
> > 
> > 
> > Has the dump:
> > 
> > __attribute__((fn spec (". w ")))
> > character(kind=1) f (character(kind=1) x)
> > {
> >   (void) 0;
> > }
> > 
> > 
> > Note the change to kind=1
> 
> So, you want gfortran to reject the function.
> 
> It gets real ugly with
> 
> function f(x) bind(C) result(a)
>    character(kind=4) a
>    character(kind=4), value :: x
>    a = x
> end
> 
> leading to
> 
> __attribute__((fn spec (". w ")))
> character(kind=1) f (character(kind=1) x)
> {
>   character(kind=1) a;
> 
>   *(character(kind=4) *) &a = *(character(kind=4) *) &x;
>   return a;
> }

Looks like resolve.cc:resolve_symbol() might be able to dela with this.
For my function with the result variable one has

(gdb) p *sym
$4 = {name = 0x2041ec100 "f", module = 0x0, declared_at = {
    nextc = 0x203a38160, lb = 0x203a38140}, ts = {type = BT_UNKNOWN, kind = 0, 
...
    in_equivalence = 0, function = 1, subroutine = 0, procedure = 0, 
    generic = 0, generic_copy = 0, implicit_type = 0, untyped = 0, 
    is_bind_c = 1, extension = 0, is_class = 0, class_ok = 0, vtab = 0, 
...
   value = 0x0, as = 0x0, result = 0x203a57600, components = 0x0, 

(gdb) p *sym->result
$5 = {name = 0x2041ec110 "a", module = 0x0, declared_at = {
    nextc = 0x203a381dc, lb = 0x203a38140}, ts = {type = BT_CHARACTER, 
    kind = 4, u = {derived = 0x203a245a0, cl = 0x203a245a0, pad = 60966304}, 
...
    dummy = 0, result = 1, assign = 0, threadprivate = 0, 

so gfortran can check for kind=4 versus kind=1 (aka C_CHAR).

  parent reply	other threads:[~2022-10-14 18:51 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 [this message]
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
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-buFjox8smI@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).