Hi all,While investigating OCaml 5.2.0 build failure on armel, I realized that atomic 64-bit reads from mmap-ed memory on armel results in a segfault.
See: https://github.com/ocaml/ocaml/issues/13234#issuecomment-2176079951 for a minimal example. Is this behaviour known? Is there a will to fix it? A contributor suggests a problem in gcc (libatomic) and/or the kernel. Cheers, -- Stéphane