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++/105304] [10/11 Regression] ICE segfault using ad-hoc concept with -Wall since r10-7441-ga7ea3d2ced786c45
Date: Thu, 28 Apr 2022 15:39:35 +0000	[thread overview]
Message-ID: <bug-105304-4-IcdzFbMtOy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105304-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:992dd9a071c16b94a616ab7242390b6581fa6001

commit r11-9946-g992dd9a071c16b94a616ab7242390b6581fa6001
Author: Patrick Palka <ppalka@redhat.com>
Date:   Mon Apr 25 21:49:00 2022 -0400

    c++: ICE with requires-expr and -Wsequence-point [PR105304]

    Here we're crashing from verify_sequence_points for this requires-expr
    condition because it contains a templated CAST_EXPR with empty operand,
    and verify_tree doesn't ignore this empty operand only because the
    manual tail recursion that it performs for unary expression trees skips
    the NULL test.

            PR c++/105304

    gcc/c-family/ChangeLog:

            * c-common.c (verify_tree) [restart]: Move up to before the
            NULL test.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/concepts-requires30.C: New test.

    (cherry picked from commit c83b9c54d9dee2dce5d8268472a745b013d166cc)

  parent reply	other threads:[~2022-04-28 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 16:14 [Bug c++/105304] New: ICE segfault using ad-hoc concept with -Wall bjoern at hoehrmann dot de
2022-04-19 14:13 ` [Bug c++/105304] [10/11/12 Regression] ICE segfault using ad-hoc concept with -Wall since r10-7441-ga7ea3d2ced786c45 marxin at gcc dot gnu.org
2022-04-21  7:22 ` rguenth at gcc dot gnu.org
2022-04-22 18:16 ` ppalka at gcc dot gnu.org
2022-04-26  1:49 ` cvs-commit at gcc dot gnu.org
2022-04-26  1:50 ` [Bug c++/105304] [10/11 " ppalka at gcc dot gnu.org
2022-04-28 15:39 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-09 23:33 ` [Bug c++/105304] [10 " cvs-commit at gcc dot gnu.org
2022-05-09 23:35 ` 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-105304-4-IcdzFbMtOy@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).