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++/96440] [9/10/11/12 Regression] ICE in tree check: expected tree_list, have error_mark in get_attribute_name, at attribs.c:841
Date: Tue, 08 Mar 2022 23:35:29 +0000	[thread overview]
Message-ID: <bug-96440-4-73M3jH9BNH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96440-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96440

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:e52af9cac7fa7409c78c9f336dc1da57750c9766

commit r12-7552-ge52af9cac7fa7409c78c9f336dc1da57750c9766
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Tue Mar 8 23:33:46 2022 +0000

    PR c++/96440: ICE-on-invalid-code error recovery.

    This patch fixes PR c++/96440 which is an ICE-on-invalid-code regression
    affecting mainline.

    2022-03-08  Roger Sayle  <roger@nextmovesoftware.com>

    gcc/cp/ChangeLog
            PR c++/96440
            * decl.cc (start_decl): Defend against prefix_attributes being
            error_mark_node.

    gcc/testsuite/ChangeLog
            PR c++/96440
            * g++.dg/cpp0x/pr96440.C: New test case.

  parent reply	other threads:[~2022-03-08 23:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 16:55 [Bug c++/96440] New: " haoxintu at gmail dot com
2020-08-03 19:40 ` [Bug c++/96440] [8/9/10/11 Regression] " mpolacek at gcc dot gnu.org
2020-08-04  6:01 ` rguenth at gcc dot gnu.org
2021-05-14  9:53 ` [Bug c++/96440] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:18 ` rguenth at gcc dot gnu.org
2022-03-07 13:06 ` roger at nextmovesoftware dot com
2022-03-08 23:35 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-09 16:04 ` roger at nextmovesoftware dot com

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-96440-4-73M3jH9BNH@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: link
Be 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).