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 libstdc++/101263] non-propagating-cache::emplace-deref missing constexpr
Date: Tue, 13 Jul 2021 17:45:57 +0000 [thread overview]
Message-ID: <bug-101263-4-xI3oDnBgb9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101263-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101263
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org
Last reconfirmed| |2021-07-13
CC| |ppalka at gcc dot gnu.org
Status|UNCONFIRMED |ASSIGNED
--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
It looks like emplace-deref was made constexpr in R1 of the paper, but we only
implemented R0. Fortunately this added constexpr seems to be the only
functional change in R1 vs R0.
We might first need to implement P2231 (for constexpr optional) before this
function can be properly constexpr.
next prev parent reply other threads:[~2021-07-13 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 17:23 [Bug libstdc++/101263] New: " hewillk at gmail dot com
2021-07-13 17:45 ` ppalka at gcc dot gnu.org [this message]
2021-09-08 7:42 ` [Bug libstdc++/101263] " rguenth at gcc dot gnu.org
2021-09-08 10:30 ` redi at gcc dot gnu.org
2021-10-14 8:09 ` redi at gcc dot gnu.org
2021-10-14 15:22 ` ppalka at gcc dot gnu.org
2021-10-14 15:35 ` barry.revzin at gmail dot com
2021-10-14 15:43 ` rs2740 at gmail dot com
2021-10-15 17:27 ` cvs-commit at gcc dot gnu.org
2021-10-15 17:31 ` redi at gcc dot gnu.org
2021-11-24 12:22 ` redi at gcc dot gnu.org
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2022-04-21 9:18 ` 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-101263-4-xI3oDnBgb9@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).