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++/107542] ICE in spaceship_comp_cat, at cp/method.cc:1055
Date: Wed, 30 Nov 2022 00:25:57 +0000	[thread overview]
Message-ID: <bug-107542-4-ec6rlc5PNd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107542-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS 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:000e9863120cbc75a0f8d497264519974c97669f

commit r13-4397-g000e9863120cbc75a0f8d497264519974c97669f
Author: Patrick Palka <ppalka@redhat.com>
Date:   Tue Nov 29 19:25:37 2022 -0500

    c++: ICE with <=> of incompatible pointers [PR107542]

    In a SFINAE context composite_pointer_type returns error_mark_node if
    the given pointer types are incompatible.  But the SPACESHIP_EXPR case
    of cp_build_binary_op wasn't prepared for this error_mark_node result,
    which led to an ICE (from spaceship_comp_cat) for the below testcase.
    (In a non-SFINAE context composite_pointer_type issues a permerror and
    returns cv void* in this case, so this ICE seems specific to SFINAE.)

            PR c++/107542

    gcc/cp/ChangeLog:

            * typeck.cc (cp_build_binary_op): In the SPACESHIP_EXPR case,
            handle an error_mark_node result type.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/spaceship-sfinae2.C: New test.

  parent reply	other threads:[~2022-11-30  0:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 20:29 [Bug c++/107542] New: " danakj at orodu dot net
2022-11-06 20:31 ` [Bug c++/107542] " pinskia at gcc dot gnu.org
2022-11-06 20:38 ` danakj at orodu dot net
2022-11-06 20:39 ` danakj at orodu dot net
2022-11-21 13:00 ` marxin at gcc dot gnu.org
2022-11-29 19:25 ` ppalka at gcc dot gnu.org
2022-11-30  0:25 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-30  0:27 ` ppalka at gcc dot gnu.org
2022-12-19 16:54 ` cvs-commit at gcc dot gnu.org
2022-12-19 16:55 ` 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-107542-4-ec6rlc5PNd@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).