public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/99849] [8/9 Regression] ICE in expand_expr_real_1, at expr.c:11556 since r5-5407-g30d5d8c5189064c8 Date: Thu, 22 Apr 2021 16:52:42 +0000 [thread overview] Message-ID: <bug-99849-4-AEk2mfiYNo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99849-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99849 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-8 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:467011a53a24c81628cce46d326574a9f32c374f commit r8-10906-g467011a53a24c81628cce46d326574a9f32c374f Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Apr 10 12:49:01 2021 +0200 expand: Fix up LTO ICE with COMPOUND_LITERAL_EXPR [PR99849] The gimplifier optimizes away COMPOUND_LITERAL_EXPRs, but they can remain in the form of ADDR_EXPR of COMPOUND_LITERAL_EXPRs in static initializers. By the TREE_STATIC check I meant to check that the underlying decl of the compound literal is a global rather than automatic variable which obviously can't be referenced in static initializers, but unfortunately with LTO it might end up in another partition and thus be DECL_EXTERNAL instead. 2021-04-10 Jakub Jelinek <jakub@redhat.com> PR lto/99849 * expr.c (expand_expr_addr_expr_1): Test is_global_var rather than just TREE_STATIC on COMPOUND_LITERAL_EXPR_DECLs. * gcc.dg/lto/pr99849_0.c: New test. (cherry picked from commit 2e57bc7eedb084869d17fe07b538d907b8fee819)
next prev parent reply other threads:[~2021-04-22 16:52 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 15:21 [Bug lto/99849] New: " marxin at gcc dot gnu.org 2021-03-31 15:21 ` [Bug lto/99849] " marxin at gcc dot gnu.org 2021-03-31 15:28 ` marxin at gcc dot gnu.org 2021-04-01 6:56 ` rguenth at gcc dot gnu.org 2021-04-09 15:05 ` [Bug lto/99849] [8/9/10/11 Regression] " jakub at gcc dot gnu.org 2021-04-09 15:22 ` jakub at gcc dot gnu.org 2021-04-10 10:49 ` cvs-commit at gcc dot gnu.org 2021-04-10 10:51 ` [Bug lto/99849] [8/9/10 " jakub at gcc dot gnu.org 2021-04-20 9:45 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:51 ` [Bug lto/99849] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:52 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-22 17:11 ` 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-99849-4-AEk2mfiYNo@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).