public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/104228] [9/10/11/12 Regression] ICE in df_install_ref, at df-scan.cc:2294 since r8-3589-g707905d0773e5a8e Date: Fri, 28 Jan 2022 21:19:31 +0000 [thread overview] Message-ID: <bug-104228-4-z1XL2T1fiq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104228-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104228 Mikael Morin <mikael at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikael at gcc dot gnu.org Assignee|unassigned at gcc dot gnu.org |mikael at gcc dot gnu.org Status|NEW |ASSIGNED --- Comment #6 from Mikael Morin <mikael at gcc dot gnu.org> --- The full typespec is copied from the associate target (x) to the associate symbol (y) at parse.cc:4925. This includes the character length object, which starting from there is shared between x and y. None of the various conditions are met in resolve_assoc_var to overwrite the character length object. So when we create the length decl (.y) for y and store it in its character length object, it also appears in that of x at the same time. And from there it is added to both functions along a path that I have lost. Draft patch: diff --git a/gcc/fortran/resolve.cc b/gcc/fortran/resolve.cc index 835a4783718..266e41e25b1 100644 --- a/gcc/fortran/resolve.cc +++ b/gcc/fortran/resolve.cc @@ -9227,7 +9227,6 @@ resolve_assoc_var (gfc_symbol* sym, bool resolve_target) sym->ts.u.cl = target->ts.u.cl; if (sym->ts.deferred && target->expr_type == EXPR_VARIABLE - && target->symtree->n.sym->attr.dummy && sym->ts.u.cl == target->ts.u.cl) { sym->ts.u.cl = gfc_new_charlen (sym->ns, NULL);
next prev parent reply other threads:[~2022-01-28 21:19 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-25 18:04 [Bug fortran/104228] New: [9/10/11/12 Regression] ICE in df_install_ref, at df-scan.cc:2294 gscfq@t-online.de 2022-01-26 7:49 ` [Bug fortran/104228] " rguenth at gcc dot gnu.org 2022-01-26 8:25 ` [Bug fortran/104228] [9/10/11/12 Regression] ICE in df_install_ref, at df-scan.cc:2294 since r8-3589-g707905d0773e5a8e marxin at gcc dot gnu.org 2022-01-28 15:42 ` jakub at gcc dot gnu.org 2022-01-28 15:52 ` jakub at gcc dot gnu.org 2022-01-28 16:19 ` jakub at gcc dot gnu.org 2022-01-28 21:19 ` mikael at gcc dot gnu.org [this message] 2022-02-13 16:01 ` cvs-commit at gcc dot gnu.org 2022-03-09 13:22 ` [Bug fortran/104228] [9/10/11 " rguenth at gcc dot gnu.org 2022-03-19 20:17 ` cvs-commit at gcc dot gnu.org 2022-04-10 18:48 ` cvs-commit at gcc dot gnu.org 2022-04-10 18:48 ` cvs-commit at gcc dot gnu.org 2022-04-24 16:54 ` cvs-commit at gcc dot gnu.org 2022-05-09 11:22 ` cvs-commit at gcc dot gnu.org 2022-05-09 11:27 ` mikael 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-104228-4-z1XL2T1fiq@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).