public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/107075] ICE in get, at cgraph.h:461 Date: Thu, 06 Oct 2022 19:19:11 +0000 [thread overview] Message-ID: <bug-107075-4-gzBDjjl1K9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107075-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107075 --- Comment #6 from anlauf at gcc dot gnu.org --- I tried the following patch, which however regresses on a couple testcases: diff --git a/gcc/fortran/resolve.cc b/gcc/fortran/resolve.cc index d9d101775f6..cfc6fc055bd 100644 --- a/gcc/fortran/resolve.cc +++ b/gcc/fortran/resolve.cc @@ -16349,6 +16349,16 @@ resolve_symbol (gfc_symbol *sym) if (sym->param_list) resolve_pdt (sym); + + if (sym->attr.flavor == FL_VARIABLE + && sym->attr.save == SAVE_NONE + && !sym->attr.allocatable + && !sym->attr.pointer + && !sym->attr.class_pointer + && sym->ns->proc_name + && sym->ns->proc_name->attr.flavor == FL_PROGRAM + && sym->ns->proc_name->attr.is_main_program) + sym->attr.save = SAVE_IMPLICIT; }
prev parent reply other threads:[~2022-10-06 19:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-28 17:36 [Bug fortran/107075] New: " gscfq@t-online.de 2022-09-28 20:13 ` [Bug fortran/107075] " anlauf at gcc dot gnu.org 2022-09-29 8:17 ` rguenth at gcc dot gnu.org 2022-09-29 9:05 ` mikael at gcc dot gnu.org 2022-09-29 21:16 ` anlauf at gcc dot gnu.org 2022-10-06 18:02 ` anlauf at gcc dot gnu.org 2022-10-06 19:19 ` anlauf at gcc dot gnu.org [this message]
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-107075-4-gzBDjjl1K9@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).