public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/92621] Problems with memory handling with allocatable intent(out) arrays with bind(c) Date: Thu, 01 Jul 2021 21:16:20 +0000 [thread overview] Message-ID: <bug-92621-4-AbJXmSnncq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92621-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92621 sandra at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sandra at gcc dot gnu.org --- Comment #16 from sandra at gcc dot gnu.org --- There seems to be no actual v2 patch at the link posted previously https://gcc.gnu.org/pipermail/fortran/2021-April/055991.html or the recent mail pinging that patch, and the original version at https://gcc.gnu.org/pipermail/fortran/2020-February/054001.html doesn't apply cleanly. Can you repost the patch or attach it to this issue? I think this PR may be the same issue that is affecting gfortran.dg/ts29113/interoperability/cf-out-descriptor-3.f90 gfortran.dg/ts29113/interoperability/cf-out-descriptor-4.f90 gfortran.dg/ts29113/interoperability/fc-out-descriptor-4.f90 from my new TS29113 testsuite https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574115.html and I'd like to try out the proposed fix. My own diagnosis was "Fortran function with C binding fails to automatically deallocate intent(out) allocated allocatable on entry when called from C". These testcases additionally trigger nasty errors from the memory allocator.
next prev parent reply other threads:[~2021-07-01 21:16 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92621-4@http.gcc.gnu.org/bugzilla/> 2020-12-22 13:57 ` briggs.michaels at gmail dot com 2020-12-22 13:58 ` briggs.michaels at gmail dot com 2020-12-22 14:01 ` briggs.michaels at gmail dot com 2020-12-22 14:03 ` briggs.michaels at gmail dot com 2021-04-26 11:23 ` jrfsousa at gmail dot com 2021-04-26 16:54 ` dominiq at lps dot ens.fr 2021-04-28 12:47 ` jrfsousa at gmail dot com 2021-04-28 13:53 ` dominiq at lps dot ens.fr 2021-04-28 18:33 ` jrfsousa at gmail dot com 2021-04-28 18:49 ` anlauf at gcc dot gnu.org 2021-05-07 10:48 ` jrfsousa at gcc dot gnu.org 2021-05-07 18:23 ` anlauf at gcc dot gnu.org 2021-07-01 21:16 ` sandra at gcc dot gnu.org [this message] 2021-07-01 22:21 ` kargl at gcc dot gnu.org 2021-07-02 14:53 ` sandra at gcc dot gnu.org 2021-08-11 14:11 ` burnus at gcc dot gnu.org 2021-10-18 8:29 ` cvs-commit at gcc dot gnu.org 2021-10-21 18:43 ` sandra at gcc dot gnu.org 2021-10-22 11:33 ` burnus at gcc dot gnu.org 2021-10-22 21:49 ` cvs-commit at gcc dot gnu.org 2021-10-22 22:08 ` burnus at gcc dot gnu.org 2022-01-09 23:26 ` 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-92621-4-AbJXmSnncq@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).