From Newsgroup: rec.arts.sf.written

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.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: rec.arts.sf.written

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?
--- Synchronet 3.22a-Linux NewsLink 1.2