public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103295] New: constexpr std::string does not work for clang
Date: Wed, 17 Nov 2021 00:31:30 +0000	[thread overview]
Message-ID: <bug-103295-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103295

            Bug ID: 103295
           Summary: constexpr std::string does not work for clang
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: unlvsur at live dot com
  Target Milestone: ---

#include<string>
#include<cassert>

constexpr bool foo()
{
        std::string str2{"abcwe"};
        return str2.size()==5;
}

static_assert(foo());

int main()
{
        assert(foo());
}

             reply	other threads:[~2021-11-17  0:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  0:31 unlvsur at live dot com [this message]
2021-11-17  0:31 ` [Bug libstdc++/103295] " unlvsur at live dot com
2021-11-17  0:46 ` unlvsur at live dot com
2021-11-17  0:55 ` pinskia at gcc dot gnu.org
2021-11-17  0:57 ` unlvsur at live dot com
2021-11-17  1:13 ` unlvsur at live dot com
2021-11-17  1:14 ` redi at gcc dot gnu.org
2021-11-17  1:17 ` redi at gcc dot gnu.org
2021-11-17  9:53 ` redi at gcc dot gnu.org
2021-11-17  9:57 ` redi at gcc dot gnu.org
2021-11-17  9:58 ` unlvsur at live dot com
2021-11-17 10:00 ` redi at gcc dot gnu.org
2021-11-17 12:02 ` redi at gcc dot gnu.org
2021-11-17 14:48 ` redi at gcc dot gnu.org
2021-11-17 17:23 ` cvs-commit at gcc dot gnu.org
2021-11-17 17:41 ` redi at gcc dot gnu.org
2021-11-18  0:21 ` redi at gcc dot gnu.org
2021-11-18  0:23 ` unlvsur at live dot com
2021-11-18  7:43 ` rguenth at gcc dot gnu.org
2021-11-19 18:16 ` cvs-commit at gcc dot gnu.org
2021-11-19 18:50 ` redi at gcc dot gnu.org
2021-11-19 20:19 ` cvs-commit at gcc dot gnu.org
2021-11-19 20:21 ` redi at gcc dot gnu.org
2022-11-11 17:59 ` cvs-commit at gcc dot gnu.org
2022-11-14 18:34 ` 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-103295-4@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).