public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32804] ISO C Binding: C_LOC argument checking needs improvement Date: Thu, 19 Jul 2007 08:31:00 -0000 [thread overview] Message-ID: <20070719083057.6011.qmail@sourceware.org> (raw) In-Reply-To: <bug-32804-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from burnus at gcc dot gnu dot org 2007-07-19 08:30 ------- For the accept-invalid part (c_loc of an assumed-shape array). The standard says: "X shall either (1) have interoperable type and type parameters and be (a) a variable that has the TARGET attribute and is interoperable," This variable has the TARGET attribute, but is not interoperable: "An array Fortran variable is interoperable if its type and type parameters are interoperable and it is of explicit shape or assumed size." Thus this error by NAG f95 is ok; however, as it is accepted by ifort, g95 and (currently) gfortran. As I completely fail to see any valid use of it and see several cases where it seems to work but one uses in reality the wrong array element, I favour to not allowing it even for -std=gnu. But if one finds a valid use, I'm also fine with an error only for -std=f2003. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32804
next prev parent reply other threads:[~2007-07-19 8:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-18 7:47 [Bug fortran/32804] New: " burnus at gcc dot gnu dot org 2007-07-19 8:31 ` burnus at gcc dot gnu dot org [this message] 2007-07-19 19:15 ` [Bug fortran/32804] " patchapp at dberlin dot org 2007-07-21 20:31 ` kargl at gcc dot gnu dot org 2007-07-21 20:37 ` kargl at gcc dot gnu dot 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=20070719083057.6011.qmail@sourceware.org \ --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: linkBe 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).