public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106608] [12/13 Regression] std::optional requires unavailable dtor
Date: Mon, 27 Mar 2023 14:10:08 +0000 [thread overview]
Message-ID: <bug-106608-4-aXx4fqh4Q7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106608-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106608
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2023-03-27
Status|UNCONFIRMED |WAITING
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Trunk accepts the small testcase unless the commented line is uncommented, but
then even GCC 10 and GCC 11 reject the testcase.
So what is this bug about?
next prev parent reply other threads:[~2023-03-27 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 10:23 [Bug libstdc++/106608] New: [12 " egor.pugin at gmail dot com
2022-08-13 11:42 ` [Bug libstdc++/106608] " egor.pugin at gmail dot com
2022-08-13 12:22 ` egor.pugin at gmail dot com
2022-08-14 8:22 ` egor.pugin at gmail dot com
2022-08-14 16:58 ` pinskia at gcc dot gnu.org
2022-08-15 8:24 ` [Bug libstdc++/106608] [12/13 " rguenth at gcc dot gnu.org
2023-03-27 14:10 ` rguenth at gcc dot gnu.org [this message]
2023-03-29 8:33 ` redi at gcc dot gnu.org
2023-03-29 8:38 ` [Bug libstdc++/106608] std::optional requires unavailable dtor when compiled with clang redi 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-106608-4-aXx4fqh4Q7@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).