• A new kind of weak (in)consistency model

    From Thomas Koenig@3:633/10 to All on Sun Aug 16 12:10:14 2026
    This is one is interesting, and even weaker than the Alpha,

    On LoongArch, you if you read from the same address twice,
    you cannot be sure without synchronization that you get
    the reads ordered correctly,

    So, if on the the writer side, you have (where x is in memory)

    x = 1;
    x = 2;

    and on the reader side

    a = x;
    b = x;

    you can have a=2 and b=1 as a result.

    They don't even have this in their English documentation, but
    it caused a bug in gfortran recently, gcc.gnu.org/PR118935 .

    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Scott Lurndal@3:633/10 to All on Sun Aug 16 15:28:05 2026
    Thomas Koenig <tkoenig@netcologne.de> writes:
    This is one is interesting, and even weaker than the Alpha,

    Most interesting - how did it get
    cross-posted posted to rec.arts.sf.written from
    comp.arch?

    --- PyGate Linux v1.5.19
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)