public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "avemilia at protonmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105841] New: Change in behavior of CTAD for alias templates
Date: Fri, 03 Jun 2022 18:12:01 +0000 [thread overview]
Message-ID: <bug-105841-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105841
Bug ID: 105841
Summary: Change in behavior of CTAD for alias templates
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: avemilia at protonmail dot com
Target Milestone: ---
Created attachment 53080
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53080&action=edit
repro
Since GCC 12, this code does not compile: https://godbolt.org/z/sWvh7P4co
The code used to compile on GCC 10 and 11. If this is incorrect code, please
explain what is wrong.
next reply other threads:[~2022-06-03 18:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 18:12 avemilia at protonmail dot com [this message]
2022-06-06 12:50 ` [Bug c++/105841] [12/13 Regression] " ppalka at gcc dot gnu.org
2022-06-06 19:28 ` jason at gcc dot gnu.org
2022-06-06 20:12 ` jason at gcc dot gnu.org
2022-06-07 0:02 ` mike at spertus dot com
2022-06-07 4:05 ` jason at gcc dot gnu.org
2022-06-09 13:39 ` ppalka at gcc dot gnu.org
2022-07-25 16:11 ` rguenth at gcc dot gnu.org
2023-02-09 22:05 ` jason at gcc dot gnu.org
2023-02-09 23:07 ` jason at gcc dot gnu.org
2023-02-09 23:26 ` mike at spertus dot com
2023-02-10 16:29 ` mike at spertus dot com
2023-03-09 15:27 ` cvs-commit at gcc dot gnu.org
2023-03-09 15:27 ` cvs-commit at gcc dot gnu.org
2023-03-09 15:30 ` [Bug c++/105841] [12 " jason at gcc dot gnu.org
2023-05-08 12:24 ` rguenth at gcc dot gnu.org
2023-12-20 22:23 ` jason at gcc dot gnu.org
2024-04-17 12:22 ` hokein.wu at gmail dot com
2024-04-24 21:41 ` ppalka at gcc dot gnu.org
2024-04-25 10:31 ` hokein.wu at gmail dot com
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-105841-4@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).