public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99035] New: [9/10/11 Regression] ICE in declare_weak, at varasm.c:5930 Date: Tue, 09 Feb 2021 17:43:28 +0000 [thread overview] Message-ID: <bug-99035-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99035 Bug ID: 99035 Summary: [9/10/11 Regression] ICE in declare_weak, at varasm.c:5930 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Affects versions down to r7 (r9 between 20190217 and 20190224), with option -fsyntax-only : $ g++-11-20210207 -c weak-6.c -fsyntax-only weak-6.c:7:14: internal compiler error: in declare_weak, at varasm.c:5930 7 | #pragma weak foo | ^~~ 0xf96654 declare_weak(tree_node*) ../../gcc/varasm.c:5930 0x86f6e1 apply_pragma_weak ../../gcc/c-family/c-pragma.c:265 0x870ae1 handle_pragma_weak ../../gcc/c-family/c-pragma.c:376 0x7777ac cp_parser_pragma ../../gcc/cp/parser.c:45120 0x7a03db cp_parser_translation_unit ../../gcc/cp/parser.c:4936 0x7a03db c_parse_file() ../../gcc/cp/parser.c:45179 0x86d982 c_common_parse_file() ../../gcc/c-family/c-opts.c:1218
next reply other threads:[~2021-02-09 17:43 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 17:43 gscfq@t-online.de [this message] 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 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@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).