https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106807
--- Comment #3 from palmer at gcc dot gnu.org --- (In reply to Andreas Schwab from comment #1) > That happens if you use a modified compiler that automatically adds > -latomic, so that configure in libatomic thinks that the builtins are > available and expanded inline. I'm just running trunk (or at least trying to, something from the environment may have leaked in). I do find that my multilib libatomic autoconf runs have -pthread, which causes -latomic on RISC-V. I'm not sure what's made that happen, though. Maybe the right answer here is to just go commit https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600151.html rather than spending time trying to figure out how my environment has broken?
