public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub 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 15:42:08 +0000 [thread overview] Message-ID: <bug-104228-4-I7C0cchTvF@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Seems to be a FE bug. Already in *.gimple bug with -fdump-tree-all-uid one can see: __attribute__((fn spec (". "))) void p () { static voidD.27 sD.4214 (void); struct array01_character(kind=1) yD.4238; static integer(kind=8)D.9 .yD.4216; static struct array01_character(kind=1) xD.4249 = {.dataD.4244=0B}; bitsizetype D.4278; sizetype D.4279; try { ... __attribute__((fn spec (". "))) void s () { bitsizetype D.4285; sizetype .y.10D.4286; integer(kind=8)D.9 iftmp.14D.4287; { static integer(kind=8)D.9 .yD.4216; static struct array01_character(kind=1) xD.4249 = {.dataD.4244=0B}; bitsizetype D.4278; sizetype D.4279; That means that BLOCK_VARS of a BLOCK inside of p function contain s var with DECL_UID 4214, its DECL_CHAIN is y with DECL_UID 4238 and its DECL_CHAIN is .y with DECL_UID 4216. But the same .y var with DECL_UID 4216 is also in BLOCK_VARS of another BLOCK inside of s. Vars in BLOCK_VARS are chained through DECL_CHAIN, aren't in some vec or TREE_VEC etc., so can't be part of multiple chains.
next prev parent reply other threads:[~2022-01-28 15:42 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 [this message] 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 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-I7C0cchTvF@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).