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++/110175] [GCC][Crash] GCC Crash on valid code
Date: Wed, 28 Jun 2023 15:52:20 +0000	[thread overview]
Message-ID: <bug-110175-4-JqbaPSO5VQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110175-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:4de22e25918f6fe40184c444ba6d81b19b806e26

commit r14-2167-g4de22e25918f6fe40184c444ba6d81b19b806e26
Author: Marek Polacek <polacek@redhat.com>
Date:   Thu Jun 8 14:07:44 2023 -0400

    c++: fix error reporting routines re-entered ICE [PR110175]

    Here we get the "error reporting routines re-entered" ICE because
    of an unguarded use of warning_at.  While at it, I added a check
    for a warning_at just above it.

            PR c++/110175

    gcc/cp/ChangeLog:

            * typeck.cc (cp_build_unary_op): Check tf_warning before warning.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/decltype-110175.C: New test.

  parent reply	other threads:[~2023-06-28 15:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 14:28 [Bug c++/110175] New: " yronglin777 at gmail dot com
2023-06-08 18:05 ` [Bug c++/110175] " mpolacek at gcc dot gnu.org
2023-06-09  4:13 ` yronglin777 at gmail dot com
2023-06-28 15:52 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-28 15:52 ` mpolacek at gcc dot gnu.org
2023-06-28 18:52 ` 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-110175-4-JqbaPSO5VQ@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).