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++/110854] constructor of std::counting_semaphore is not constexpr
Date: Tue, 17 Oct 2023 04:23:46 +0000	[thread overview]
Message-ID: <bug-110854-4-AIQOmFu6Th@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110854-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jiang An <de34 at live dot cn> ---
(In reply to Jiang An from comment #2)
> The constructor of the internal __platform_semaphore class currently calls
> sem_init, which make it incompatible with constexpr...

It seems doable to make the ctor constexpr, but we need to use different
strategies for different C libs.

      parent reply	other threads:[~2023-10-17  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  1:58 [Bug libstdc++/110854] New: " cooky.ykooc922 at gmail dot com
2023-07-31  2:06 ` [Bug libstdc++/110854] " pinskia at gcc dot gnu.org
2023-08-04  2:40 ` de34 at live dot cn
2023-10-17  4:23 ` de34 at live dot cn [this message]

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-110854-4-AIQOmFu6Th@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).