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/109684] compiling failure: complaining about a final subroutine of a type being not PURE (while it is indeed PURE) Date: Tue, 23 May 2023 16:53:20 +0000 [thread overview] Message-ID: <bug-109684-4-4QHZOkJyJO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109684-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109684 Paul Thomas <pault at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org Last reconfirmed| |2023-05-23 Ever confirmed|0 |1 --- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> --- Created attachment 55144 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55144&action=edit Fix for this PR Thanks for reporting this. The patch "fingered" in comment #4 is certainly responsible for this regression. In particular, it is the first chunk in resolve.cc that is the culprit. The attached patch feels to be a bit of sticking plaster on top of sticking plaster and so I will go back to hunt down the root cause of these namespace-less symbols. I fear that you will have to make your procedures impure for the time being or, if you don't need the added finalization features, revert to a previous version of gfortran. Regards and apologies for the inconvenience. Paul
next prev parent reply other threads:[~2023-05-23 16:53 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-01 13:39 [Bug fortran/109684] New: " wangmianzhi1 at linuxmail dot org 2023-05-17 14:44 ` [Bug fortran/109684] " wangmianzhi1 at linuxmail dot org 2023-05-22 6:33 ` trnka at scm dot com 2023-05-22 6:36 ` trnka at scm dot com 2023-05-22 6:39 ` trnka at scm dot com 2023-05-23 16:53 ` pault at gcc dot gnu.org [this message] 2023-05-24 10:05 ` pault at gcc dot gnu.org 2023-05-24 10:13 ` trnka at scm dot com 2023-05-24 12:37 ` neil.n.carlson at gmail dot com 2023-08-07 20:39 ` neil.n.carlson at gmail dot com 2023-08-07 22:04 ` kargl at gcc dot gnu.org 2023-08-07 22:23 ` sgk at troutmask dot apl.washington.edu 2023-08-07 22:58 ` sgk at troutmask dot apl.washington.edu 2023-08-08 13:27 ` pault at gcc dot gnu.org 2023-08-09 2:29 ` kargl at gcc dot gnu.org 2023-08-09 7:58 ` pault at gcc dot gnu.org 2023-08-09 8:11 ` pault at gcc dot gnu.org 2023-08-09 10:08 ` trnka at scm dot com 2023-08-09 11:04 ` cvs-commit at gcc dot gnu.org 2023-08-09 14:54 ` cvs-commit at gcc dot gnu.org 2023-08-09 14:56 ` pault at gcc dot gnu.org 2023-08-09 15:37 ` sgk at troutmask dot apl.washington.edu 2023-08-09 16:19 ` trnka at scm dot com 2023-08-09 16:59 ` sgk at troutmask dot apl.washington.edu 2023-11-06 15:34 ` trnka at scm dot com 2023-11-06 18:40 ` 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-109684-4-4QHZOkJyJO@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).