public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108961] Segfault when associating to pointer from C_F_POINTER Date: Tue, 18 Apr 2023 09:17:40 +0000 [thread overview] Message-ID: <bug-108961-4-2Orh3abaoA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108961-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108961 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|87477 | Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org --- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> --- Since this has nothing to do with the associate construct, I have removed the blocking of PR87477. That said, I am onto it :-) I cannot see anything untoward with the produced code at the moment and, since there is the dependence on whether or not the subroutine is in a module, I can only surmise that there is some subtle difference in memory usage. Paul Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477 [Bug 87477] [meta-bug] [F03] issues concerning the ASSOCIATE statement
next prev parent reply other threads:[~2023-04-18 9:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 0:22 [Bug fortran/108961] New: " jeffrey.p.hill at nasa dot gov 2023-02-28 0:23 ` [Bug fortran/108961] " jeffrey.p.hill at nasa dot gov 2023-03-23 18:39 ` pault at gcc dot gnu.org 2023-04-18 9:17 ` pault at gcc dot gnu.org [this message] 2023-06-20 12:55 ` pault at gcc dot gnu.org 2023-06-21 16:02 ` cvs-commit at gcc dot gnu.org 2023-06-21 21:07 ` pault at gcc dot gnu.org 2023-07-29 20:18 ` anlauf at gcc dot gnu.org 2023-07-30 9:46 ` paul.richard.thomas at gmail dot com 2023-07-30 12:25 ` cvs-commit 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-108961-4-2Orh3abaoA@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).