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++/115223] [15 regression] ICE when building KDE kontrast with LTO (error: ‘TYPE_CANONICAL’ has different ‘TYPE_CANONICAL’) since r15-779-g3c98d06a9016a0
Date: Wed, 29 May 2024 08:50:19 +0000	[thread overview]
Message-ID: <bug-115223-4-NUzF4LhXUk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115223-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:58b8c87b7fb281e35a6817cc91a292096fdc02dc

commit r15-892-g58b8c87b7fb281e35a6817cc91a292096fdc02dc
Author: Patrick Palka <ppalka@redhat.com>
Date:   Wed May 29 04:49:37 2024 -0400

    c++: canonicity of fn types w/ instantiated eh specs [PR115223]

    When propagating structural equality in build_cp_fntype_variant, we
    should consider structural equality of the exception-less variant, not
    of the given type which might use structural equality only because it
    has a (complex) noexcept-spec that we're intending to replace, as in
    maybe_instantiate_noexcept which calls build_exception_variant using
    the deferred-noexcept function type.  Otherwise we might pessimistically
    use structural equality for a function type with a simple instantiated
    noexcept-spec, leading to a LTO-triggered type verification failure if we
    later use that (structural-equality) type as the canonical version of
    some other variant.

            PR c++/115223

    gcc/cp/ChangeLog:

            * tree.cc (build_cp_fntype_variant): Propagate structural
            equality of the exception-less variant.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/noexcept87.C: New test.

    Reviewed-by: Jason Merrill <jason@redhat.com>

  parent reply	other threads:[~2024-05-29  8:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-25  2:33 [Bug lto/115223] New: [15 regression] ICE when building KDE kontrast with LTO (error: ‘TYPE_CANONICAL’ has different ‘TYPE_CANONICAL’) sjames at gcc dot gnu.org
2024-05-25  8:52 ` [Bug lto/115223] " sjames at gcc dot gnu.org
2024-05-25 13:58 ` [Bug c++/115223] [15 regression] ICE when building KDE kontrast with LTO (error: ‘TYPE_CANONICAL’ has different ‘TYPE_CANONICAL’) since r15-779-g3c98d06a9016a0 sjames at gcc dot gnu.org
2024-05-27  6:57 ` rguenth at gcc dot gnu.org
2024-05-29  8:50 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-29  8:51 ` 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-115223-4-NUzF4LhXUk@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).