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++/104668] [12 Regression] ICE in lookup_attribute_spec, at attribs.cc:425 Date: Wed, 06 Apr 2022 15:55:37 +0000 [thread overview] Message-ID: <bug-104668-4-XOtfSAbYWG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104668-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104668 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:9fd377a747375a82912bd81c67b275301489785c commit r12-8029-g9fd377a747375a82912bd81c67b275301489785c Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Apr 6 17:53:41 2022 +0200 c++: Fix up ICE when cplus_decl_attributes is called with error_mark_node attributes [PR104668] cplus_decl_attributes can be called with attributes equal to error_mark_node, there are some spots in the function that test it or decl_attributes it calls starts with: if (TREE_TYPE (*node) == error_mark_node || attributes == error_mark_node) return NULL_TREE; But the recent PR104245 change broke this when processing_template_decl is true. The patch returns early for attributes error_mark_node from cplus_decl_attributes. 2022-04-06 Jakub Jelinek <jakub@redhat.com> PR c++/104668 * decl2.cc (splice_template_attributes): Return NULL if *p is error_mark_node. (cplus_decl_attributes): Return early if attributes is error_mark_node. Don't check that later. * g++.dg/cpp0x/pr104668.C: New test.
next prev parent reply other threads:[~2022-04-06 15:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-23 17:59 [Bug c++/104668] New: " gscfq@t-online.de 2022-02-23 19:36 ` [Bug c++/104668] " mpolacek at gcc dot gnu.org 2022-02-24 15:36 ` marxin at gcc dot gnu.org 2022-04-06 15:55 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-08 16:49 ` 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-104668-4-XOtfSAbYWG@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).