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 c++/100580] [10 Regression] ICE with -fdump-passes since r10-6837-g2473c81cb2d4627f Date: Tue, 10 May 2022 08:18:09 +0000 [thread overview] Message-ID: <bug-100580-4-RwsTOAnAf6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100580-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100580 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:b5a972b300f26d2af4f1622c560f6ffda25852ce commit r10-10613-gb5a972b300f26d2af4f1622c560f6ffda25852ce Author: Jakub Jelinek <jakub@redhat.com> Date: Tue May 18 10:10:17 2021 +0200 function: Set dummy DECL_ASSEMBLER_NAME in push_dummy_function [PR100580] Last year I've added cgraph_node::get_create calls for the dummy functions used for -fdump-passes, so that it interacts well with pass disabling/enabling which is cgraph uid based. Unfortunately, as the following testcase shows, when assembler hash is present, that wants to compute DECL_ASSEMBLER_NAME and the C++ FE is unprepared to handle it on the dummy functions which don't have DECL_NAME etc. The following patch fixes it by setting up a dummy DECL_ASSEMBLER_NAME on these, so that the FEs don't need to compute it. 2021-05-18 Jakub Jelinek <jakub@redhat.com> PR c++/100580 * function.c (push_dummy_function): Set DECL_ARTIFICIAL and DECL_ASSEMBLER_NAME on the fn_decl. * g++.dg/other/pr100580.C: New test. (cherry picked from commit 978b62e554ffb4b34844c72d259ce71fcbd87591)
next prev parent reply other threads:[~2022-05-10 8:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-13 3:25 [Bug c++/100580] New: ICE with -fdump-passes fxue at os dot amperecomputing.com 2021-05-13 8:00 ` [Bug c++/100580] [10/11/12 Regression] ICE with -fdump-passes since r10-6837-g2473c81cb2d4627f marxin at gcc dot gnu.org 2021-05-17 11:37 ` rguenth at gcc dot gnu.org 2021-05-17 17:17 ` jakub at gcc dot gnu.org 2021-05-18 8:10 ` cvs-commit at gcc dot gnu.org 2021-05-18 8:12 ` [Bug c++/100580] [10/11 " jakub at gcc dot gnu.org 2021-05-31 14:08 ` cvs-commit at gcc dot gnu.org 2021-05-31 14:56 ` [Bug c++/100580] [10 " jakub at gcc dot gnu.org 2022-05-10 8:18 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-10 10:02 ` 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-100580-4-RwsTOAnAf6@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).