1. Forum
  2. USENET
  3. cplusplus

  • memory_order_consume...

    From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.c++ on Fri Oct 10 00:08:07 2025
    From Newsgroup: comp.lang.c++

    Well, is it std anymore? WTF! I don't want to have to use a damn acquire
    when I don't need to.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Bonita Montero@Bonita.Montero@gmail.com to comp.lang.c++ on Sat Oct 11 21:15:35 2025
    From Newsgroup: comp.lang.c++

    Am 10.10.2025 um 09:08 schrieb Chris M. Thomasson:

    Well, is it std anymore? WTF! I don't want to have to use a damn acquire when I don't need to.

    x86 doesn't have consume memory ordering so this maps to acuqire
    ordering.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.c++ on Sat Oct 11 13:09:52 2025
    From Newsgroup: comp.lang.c++

    On 10/11/2025 12:15 PM, Bonita Montero wrote:
    Am 10.10.2025 um 09:08 schrieb Chris M. Thomasson:

    Well, is it std anymore? WTF! I don't want to have to use a damn
    acquire when I don't need to.

    x86 doesn't have consume memory ordering so this maps to acuqire
    ordering.

    Right, its implied on that arch. x86 has data dependent ordering. But I
    want to keep consume. For instance, it better not emit a damn acquire
    barrier on SPARC in RMO mode! Shit man.
    --- Synchronet 3.21a-Linux NewsLink 1.2