public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/100906] Bind(c): failure handling character with len/=1 Date: Mon, 26 Jul 2021 12:52:48 +0000 [thread overview] Message-ID: <bug-100906-4-1aMq643d4h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100906-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100906 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- I have committed: r12-2431-gb3d4011ba10275fbd5d6ec5a16d5aaebbdfb5d3c https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575729.html which should fix most diagnostic issues with character len /= 1 – except for: * len=0 – in my understanding, that's valid when using a descriptor but not when passing the argument as address to the byte stream -> with current patch not rejected. * const-length > 1 module variables with BIND(C). Those should now be valid as well, but that was not touched by this patch. Regarding len=0 and other things, see also thread starting at https://mailman.j3-fortran.org/pipermail/j3/2021-July/013189.html * * * Other TODO with regards to things diagnostic in my patch: * See 'sorry' in the patch and in the testsuite. Namely: len=* and len=: require an array descriptor, but for scalars and (len=*, only) for assumed/explicit-size arrays no descriptor is used. (Hence, the code aborts with an error) -> Requires an update both for the call and for the function type and for the function interface declaration. * * * Attached/submitted patch by José: There is a minor overlap to my committed patch and some overlap to the issues listed above, but I have not sorted it out, yet.
next prev parent reply other threads:[~2021-07-26 12:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-04 17:41 [Bug fortran/100906] New: " jrfsousa at gcc dot gnu.org 2021-06-04 17:42 ` [Bug fortran/100906] " jrfsousa at gcc dot gnu.org 2021-06-13 18:51 ` jrfsousa at gcc dot gnu.org 2021-06-13 18:51 ` jrfsousa at gcc dot gnu.org 2021-07-26 12:52 ` burnus at gcc dot gnu.org [this message] 2021-07-27 10:24 ` burnus at gcc dot gnu.org 2021-10-22 15:29 ` cvs-commit at gcc dot gnu.org 2021-10-22 15:32 ` 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-100906-4-1aMq643d4h@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: 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).