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++/99035] [9 Regression] ICE in declare_weak, at varasm.c:5930 Date: Tue, 20 Apr 2021 23:32:17 +0000 [thread overview] Message-ID: <bug-99035-4-izMhNPSsYw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99035-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99035 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:6496e9154309cbd911f944147da1246628e393da commit r9-9418-g6496e9154309cbd911f944147da1246628e393da Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Feb 10 19:52:37 2021 +0100 varasm: Fix ICE with -fsyntax-only [PR99035] My FE change from 2 years ago uses TREE_ASM_WRITTEN in -fsyntax-only mode more aggressively to avoid "expanding" functions multiple times. With -fsyntax-only nothing is really expanded, so I think it is acceptable to adjust the assert and allow declare_weak at any time, with -fsyntax-only we know it is during parsing only anyway. 2021-02-10 Jakub Jelinek <jakub@redhat.com> PR c++/99035 * varasm.c (declare_weak): For -fsyntax-only, allow even TREE_ASM_WRITTEN function decls. * g++.dg/ext/weak6.C: New test. (cherry picked from commit a964f494cd5a90f631b8c0c01777a9899e0351ce)
next prev parent reply other threads:[~2021-04-20 23:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 17:43 [Bug c++/99035] New: [9/10/11 " gscfq@t-online.de 2021-02-09 18:08 ` [Bug c++/99035] " mpolacek at gcc dot gnu.org 2021-02-09 18:08 ` mpolacek at gcc dot gnu.org 2021-02-10 12:30 ` jakub at gcc dot gnu.org 2021-02-10 18:53 ` cvs-commit at gcc dot gnu.org 2021-02-10 18:56 ` [Bug c++/99035] [9/10 " jakub at gcc dot gnu.org 2021-03-19 23:29 ` cvs-commit at gcc dot gnu.org 2021-03-20 8:07 ` [Bug c++/99035] [9 " jakub at gcc dot gnu.org 2021-04-20 23:32 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-22 16:50 ` cvs-commit at gcc dot gnu.org 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-99035-4-izMhNPSsYw@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).