public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Thomas Rodgers <trodgers@redhat.com>,
	gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] Add c++2a binary_semaphore
Date: Tue, 25 Feb 2020 08:53:00 -0000	[thread overview]
Message-ID: <91ac8f71-07e2-b49c-4f26-0c14da859152@embedded-brains.de> (raw)
In-Reply-To: <1285559088.6683965.1582599187278.JavaMail.zimbra@redhat.com>

Hello Thomas,

some operating systems provide already an implementation of binary 
semaphores with a compatible API, e.g. RTEMS. It would be nice if I 
could use it in libstdc++. I guess you don't want to have #ifdef 
__rtems__ stuff in this code. What about defining a binary semaphore API 
for gthr.h and then implement the optional futex support in 
libgcc/gthr-posix.h?

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

  reply	other threads:[~2020-02-25  8:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <381004109.5930741.1582008200673.JavaMail.zimbra@redhat.com>
2020-02-18  6:46 ` Thomas Rodgers
2020-02-18 13:49   ` Sebastian Huber
2020-02-18 14:31     ` Jonathan Wakely
2020-02-21 12:33       ` Sebastian Huber
2020-02-18 14:25   ` Jonathan Wakely
2020-02-20  3:19     ` Thomas Rodgers
2020-02-25  2:53       ` Thomas Rodgers
2020-02-25  8:53         ` Sebastian Huber [this message]
2020-02-25 12:33           ` Jonathan Wakely
2020-02-25 12:39             ` Jonathan Wakely
2020-02-26 16:07         ` Jonathan Wakely

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=91ac8f71-07e2-b49c-4f26-0c14da859152@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=trodgers@redhat.com \
    /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).