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++/108243] [10/11/12/13 Regression] Missed optimization for static const std::string_view(const char*)
Date: Mon, 20 Feb 2023 18:33:18 +0000 [thread overview]
Message-ID: <bug-108243-4-U3zE4csfX7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108243-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108243
--- Comment #9 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Jiang An from comment #8)
> This seems a bug, not merely missing of optimization. The string_view object
> should always be statically initialized, because it has static storage
> duration and its initializer is a constant iniitializer.
Good point. It looks like we're inconsistent about static initialization here
-- we do it for suitable copy initialization but not for suitable direct
initialization:
static std::string_view foo1 = {"bar"}; // static initialization
static std::string_view foo2("bar"); // dynamic initialization
next prev parent reply other threads:[~2023-02-20 18:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 16:31 [Bug c++/108243] New: " erosenberger at kinetica dot com
2023-01-04 11:42 ` [Bug c++/108243] " redi at gcc dot gnu.org
2023-01-04 13:05 ` redi at gcc dot gnu.org
2023-01-04 13:15 ` redi at gcc dot gnu.org
2023-01-04 13:20 ` [Bug c++/108243] [10/11/12/13 Regression] " redi at gcc dot gnu.org
2023-01-04 13:21 ` redi at gcc dot gnu.org
2023-01-04 16:47 ` ppalka at gcc dot gnu.org
2023-01-04 17:22 ` jakub at gcc dot gnu.org
2023-01-09 14:05 ` rguenth at gcc dot gnu.org
2023-01-27 19:13 ` ppalka at gcc dot gnu.org
2023-02-17 20:21 ` cvs-commit at gcc dot gnu.org
2023-02-20 5:23 ` de34 at live dot cn
2023-02-20 18:33 ` ppalka at gcc dot gnu.org [this message]
2023-02-21 13:38 ` rguenth at gcc dot gnu.org
2023-02-21 14:09 ` ppalka at gcc dot gnu.org
2023-03-02 19:05 ` cvs-commit at gcc dot gnu.org
2023-03-02 19:05 ` cvs-commit at gcc dot gnu.org
2023-03-02 19:51 ` [Bug c++/108243] [10/11/12 " ppalka at gcc dot gnu.org
2023-07-07 10:44 ` [Bug c++/108243] [11/12 " rguenth at gcc dot gnu.org
2023-12-13 16:48 ` cvs-commit 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-108243-4-U3zE4csfX7@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).