From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: atomic.h cleanup
Date: Mon, 11 Jan 2016 20:03:56 +0100 [thread overview]
Message-ID: <20160111190356.GA13558@port70.net> (raw)
In-Reply-To: <1452532349.28095.10.camel@inria.fr>
* Jens Gustedt <jens.gustedt@inria.fr> [2016-01-11 18:12:29 +0100]:
> Am Montag, den 11.01.2016, 17:35 +0100 schrieb Markus Wichmann:
> > OTOH, maybe we simply shouldn't write synchronisation primitives
> > ourselves and instead use the ones provided by GCC (and let other
> > compilers suck on a salty sausage, if they don't support those
> > primitives).
>
> I think on the long run we should use C11 atomics and leave the dirty
> work to the compiler writers. To my experience they do good work with
> that now, the assembler they produce looks nice.
>
yes but old compilers had various bugs on various targets.
> My stdatomic library is sitting there, ready to integrate into
> musl. It solves the problem of backwards compatibility for all
> compilers that that implement the __sync builtins. (gcc and clang with
> very old version numbers.)
>
i think simpler compilers like pcc, cparser, tcc
dont implement that.
if musl moves to compiler builtins then i'd
like to have a possibility to compile atomic
primitives as a separate tu
> Last time I looked, all usages but one of atomic operations in musl
> are clean. If an atomic operation is used for a data a some point,
> atomic operations are used in all other places. So moving to
> _Atomic(int) would be a option. (Basically this would be `volatile
> int*` => `_Atomic(int)`, IIRC).
>
pthread_once_t and pthread_spinlock_t are
publicly visibles type (without volatile and
_Atomic)
i dont think we can fix those without abi
change.
next prev parent reply other threads:[~2016-01-11 19:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 12:21 Markus Wichmann
2016-01-10 16:57 ` Rich Felker
2016-01-10 17:35 ` Markus Wichmann
2016-01-10 17:50 ` Alexander Monakov
2016-01-11 16:35 ` Markus Wichmann
2016-01-11 17:12 ` Jens Gustedt
2016-01-11 19:03 ` Szabolcs Nagy [this message]
2016-01-11 20:56 ` Jens Gustedt
2016-01-14 22:12 ` Rich Felker
2016-01-14 22:37 ` Jens Gustedt
2016-01-14 23:32 ` Rich Felker
2016-01-15 0:46 ` Szabolcs Nagy
2016-01-10 17:37 ` Markus Wichmann
2016-01-22 0:09 ` Rich Felker
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=20160111190356.GA13558@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).