1. Forum
  2. Newsgroups
  3. comp.std.c

  • Making the creation of atomic_flag optional

    From Philipp Klaus Krause@[email protected] to comp.std.c on Fri Feb 2 11:18:39 2024
    From Newsgroup: comp.std.c

    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
    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From David Brown@[email protected] to comp.std.c on Sat Feb 3 12:09:22 2024
    From Newsgroup: comp.std.c

    On 02/02/2024 11:18, Philipp Klaus Krause wrote:
    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

    I think it is fine to implement parts of the atomics - you just can't
    define the __SDTC_NO_ATOMICS__ symbol unless you cover it all.

    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Philipp Klaus Krause@[email protected] to comp.std.c on Thu Feb 8 08:44:36 2024
    From Newsgroup: comp.std.c

    Am 03.02.24 um 12:09 schrieb David Brown:

    I think it is fine to implement parts of the atomics - you just can't
    define the __SDTC_NO_ATOMICS__ symbol unless you cover it all.

    The problem here is that there are architectures, where atomics could be implemented except for one small issue - you can't use a char array (or allocated memory) as an atomic_flag. IMO, it would be good if this
    situation could be reflected in the standard.

    Philipp

    --- Synchronet 3.20a-Linux NewsLink 1.114