public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105995] QoI: constexpr basic_string variable must use all of its SSO buffer
Date: Thu, 16 Jun 2022 07:41:43 +0000 [thread overview]
Message-ID: <bug-105995-4-StGMnA7dao@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105995-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105995
--- Comment #2 from Jiang An <de34 at live dot cn> ---
(In reply to Andrew Pinski from comment #1)
> C++20 supports dynamic allocation for constexpr.
Yeah, but a constexpr variable can't hold dynamically allocated memory.
Dynamically allocated memory must be deallocated within its initialization.
next prev parent reply other threads:[~2022-06-16 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 7:13 [Bug libstdc++/105995] New: " de34 at live dot cn
2022-06-16 7:19 ` [Bug libstdc++/105995] " pinskia at gcc dot gnu.org
2022-06-16 7:41 ` de34 at live dot cn [this message]
2022-06-16 11:08 ` redi at gcc dot gnu.org
2022-06-16 11:14 ` redi at gcc dot gnu.org
2022-06-16 19:20 ` cvs-commit at gcc dot gnu.org
2022-06-16 19:21 ` redi at gcc dot gnu.org
2022-08-03 13:47 ` cvs-commit at gcc dot gnu.org
2022-08-03 13:49 ` 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-105995-4-StGMnA7dao@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).