public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/105054] [11/12 Regression] Using one kind of pointer functions causes the compiler to hang since r11-3029-g2b0df0a6ac79b34f Date: Mon, 04 Apr 2022 11:32:38 +0000 [thread overview] Message-ID: <bug-105054-4-txmfS0fxEY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105054-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105054 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.3 Priority|P3 |P4 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed for the hang. It hangs in f95-lang.cc:poplevel which does 391 /* Clear out the meanings of the local variables of this level. */ 392 393 for (subblock_node = decl_chain; subblock_node; 394 subblock_node = DECL_CHAIN (subblock_node)) 395 if (DECL_NAME (subblock_node) != 0) 396 /* If the identifier was used or addressed via a local extern decl, 397 don't forget that fact. */ 398 if (DECL_EXTERNAL (subblock_node)) 399 { 400 if (TREE_USED (subblock_node)) 401 TREE_USED (DECL_NAME (subblock_node)) = 1; 402 if (TREE_ADDRESSABLE (subblock_node)) 403 TREE_ADDRESSABLE (DECL_ASSEMBLER_NAME (subblock_node)) = 1; 404 } and this loop never terminates. (gdb) p decl_chain $1 = <var_decl 0x7ffff6523d80 _F.DA1> (gdb) p decl_chain->common.chain $2 = <var_decl 0x7ffff6523c60 ._F.DA0> (gdb) p decl_chain->common.chain->common.chain $3 = <var_decl 0x7ffff6523cf0 _F.DA0> (gdb) p decl_chain->common.chain->common.chain->common.chain $4 = <var_decl 0x7ffff6523c60 ._F.DA0>
next prev parent reply other threads:[~2022-04-04 11:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-25 13:02 [Bug fortran/105054] New: Using one kind of pointer functions causes the compiler to hang arjen.markus895 at gmail dot com 2022-03-25 13:45 ` [Bug fortran/105054] " mscfd at gmx dot net 2022-03-25 14:26 ` [Bug fortran/105054] [11/12 Regression] Using one kind of pointer functions causes the compiler to hang since r11-3029-g2b0df0a6ac79b34f marxin at gcc dot gnu.org 2022-04-04 11:32 ` rguenth at gcc dot gnu.org [this message] 2022-04-21 7:51 ` rguenth at gcc dot gnu.org 2023-05-29 10:06 ` [Bug fortran/105054] [11/12/13/14 " jakub 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-105054-4-txmfS0fxEY@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).