public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112737] [14 Regression] g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess errors) Date: Wed, 31 Jan 2024 15:32:04 +0000 [thread overview] Message-ID: <bug-112737-4-pV2ZmLnEma@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112737-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112737 --- Comment #6 from Patrick Palka <ppalka at gcc dot gnu.org> --- Ah, this seems to be a general declaration matching issue not specific to modules. Here's a non-modules testcase: template<template<class> class TT, class T> decltype(TT{T()}) f(); // #1 template<template<class> class TT, class T> decltype(TT{T()}) f(); // #2, should be considered a redeclaration of #1 template<class T> struct A { A(T); }; int main() { f<A, int>(); // ambiguity error } We (wrongly?) consider the return types of the two f's to be different, because the CTAD placeholders refer to different TEMPLATE_DECLs (of a logically equivalent ttp) and structural_comptypes uses pointer identity here. Perhaps we need to relax structural_comptypes in this case.
next prev parent reply other threads:[~2024-01-31 15:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-27 23:09 [Bug c++/112737] New: " hp at gcc dot gnu.org 2023-11-28 0:06 ` [Bug c++/112737] " redi at gcc dot gnu.org 2023-12-06 15:55 ` danglin at gcc dot gnu.org 2023-12-11 18:00 ` ppalka at gcc dot gnu.org 2023-12-12 1:49 ` ppalka at gcc dot gnu.org 2024-01-13 19:07 ` danglin at gcc dot gnu.org 2024-01-31 14:58 ` ppalka at gcc dot gnu.org 2024-01-31 15:32 ` ppalka at gcc dot gnu.org [this message] 2024-01-31 15:47 ` ppalka at gcc dot gnu.org 2024-02-01 18:18 ` cvs-commit at gcc dot gnu.org 2024-02-01 18:19 ` ppalka at gcc dot gnu.org 2024-02-02 13:25 ` hp 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-112737-4-pV2ZmLnEma@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: linkBe 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).