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++/104225] [9/10/11 Regression] accepts-invalid new expression that uses deleted implicit default constructor of class specialization
Date: Tue, 25 Jan 2022 20:07:11 +0000 [thread overview]
Message-ID: <bug-104225-4-V5sAmpUO80@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104225-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104225
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |NEW
Summary|[9/10/11/12 Regression] |[9/10/11 Regression]
|accepts-invalid new |accepts-invalid new
|expression that uses |expression that uses
|deleted implicit default |deleted implicit default
|constructor of class |constructor of class
|specialization |specialization
Resolution|FIXED |---
--- Comment #4 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Patrick Palka from comment #3)
> Fixed.
... for GCC 12 so far.
next prev parent reply other threads:[~2022-01-25 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 15:45 [Bug c++/104225] New: " ppalka at gcc dot gnu.org
2022-01-25 15:48 ` [Bug c++/104225] [9/10/11/12 Regression] " ppalka at gcc dot gnu.org
2022-01-25 20:05 ` cvs-commit at gcc dot gnu.org
2022-01-25 20:06 ` ppalka at gcc dot gnu.org
2022-01-25 20:07 ` ppalka at gcc dot gnu.org [this message]
2022-01-26 7:33 ` [Bug c++/104225] [9/10/11 " rguenth at gcc dot gnu.org
2022-04-12 23:44 ` cvs-commit at gcc dot gnu.org
2022-05-09 23:32 ` [Bug c++/104225] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-11 14:59 ` [Bug c++/104225] [9 " cvs-commit at gcc dot gnu.org
2022-05-11 15:05 ` 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-104225-4-V5sAmpUO80@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).