https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97182
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Jim Wilson from comment #3) > libgomp works on riscv64-linux. It would only be riscv32-linux that is > broken. > > The riscv32 support was only just recently added to FSF glibc, and hasn't > appeared in a release yet, so arguably, there is no ABI break for > riscv32-linux if we can fix this before the gcc-11 release, as that is the > first one that can officially support riscv32-linux. Unofficialy we have > embedded linux distros with riscv32-linux but they should be able to > tolerate ABI breaks, particularly since we never guaranteed that the > riscv32-linux ABI was stable. For riscv64 works perhaps, but does it work efficiently? I mean, I don't see it mentioned anywhere in libgomp/configure.tgt, which means it won't set config_path to include linux and therefore will not use futexes directly and will instead use pthread*.
