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++/112658] [12/13 Regression] ICE: finish_expr_stmt with casting an temp array to pointer and constructor call
Date: Fri, 08 Dec 2023 18:34:56 +0000	[thread overview]
Message-ID: <bug-112658-4-QbzRSo9QEQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112658-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:0c018a74eb1affe2a1fa385cdddaa93979683420

commit r14-6343-g0c018a74eb1affe2a1fa385cdddaa93979683420
Author: Patrick Palka <ppalka@redhat.com>
Date:   Fri Dec 8 13:34:04 2023 -0500

    c++: guard more against undiagnosed error_mark_node [PR112658]

    This adds a sanity check to cp_parser_expression_statement similar to
    the one in finish_expr_stmt added by r6-6795-g0fd9d4921f7ba2, which
    effectively downgrades accepts-invalid/wrong-code bugs like this one
    into ice-on-invalid/ice-on-valid ones.

            PR c++/112658

    gcc/cp/ChangeLog:

            * parser.cc (cp_parser_expression_statement): If the statement
            is error_mark_node, make sure we've seen_error().

  parent reply	other threads:[~2023-12-08 18:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 21:46 [Bug c++/112658] New: ICE: finish_expr_stmt , at cp/semantics.cc:892 julia.desmazes at gmail dot com
2023-11-21 22:23 ` [Bug c++/112658] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-11-21 22:26 ` [Bug c++/112658] [12/13/14 Regression] ICE: finish_expr_stmt with casting an temp array to pointer pinskia at gcc dot gnu.org
2023-11-21 22:35 ` [Bug c++/112658] [12/13/14 Regression] ICE: finish_expr_stmt with casting an temp array to pointer and constructor call pinskia at gcc dot gnu.org
2023-11-21 22:37 ` pinskia at gcc dot gnu.org
2023-11-22  0:37 ` ppalka at gcc dot gnu.org
2023-12-04 22:15 ` [Bug c++/112658] [12/13 " ppalka at gcc dot gnu.org
2023-12-08 18:34 ` cvs-commit at gcc dot gnu.org
2023-12-08 18:34 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-13 11:29 ` rguenth at gcc dot gnu.org
2024-05-13 16:26 ` ppalka 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-112658-4-QbzRSo9QEQ@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).