Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: Philipp Klaus Krause <pkk@spth.de>
Newsgroups: comp.std.c
Subject: Making the creation of atomic_flag optional
Date: Fri, 2 Feb 2024 11:18:39 +0100
Message-ID: <upifhv$19809$1@solani.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 2 Feb 2024 10:18:39 -0000 (UTC)
Injection-Info: solani.org; logging-data="1351689"; mail-complaints-to="abuse@news.solani.org"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:uSbWO0/ucaLD+GTi2ALs4qw3CcI=
X-User-ID: eJwFwQkBwDAMAkBLfQIjcprS+JewO2xO3i8IBhodcrYHyLJE3Jx3r/mqhg/bS4q2a72E4ugHIgAReA==
Content-Language: en-US
Xref: csiph.com comp.std.c:6643

Currently, atomics are an all-or-nothing choice (via __SDTC_NO_ATOMICS__).

I'd like to see a third option: support atomics, except for the creation 
of atomic_flag from allocated storage (or raw character arrays). This 
would make it feasible to implement atomics for some low-end systems, 
that otherwise can't support them efficiently.

Your opinions on the proposal and the proposed wording are welcome:
http://www.colecovision.eu/stuff/proposal-atomic_flag.html

Philipp