[Bug target/106807] RISC-V: libatomic routines are infinate loops

2024-07-02 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106807 Jeffrey A. Law changed: What|Removed |Added CC||law at gcc dot gnu.org Sta

[Bug target/106807] RISC-V: libatomic routines are infinate loops

2023-10-23 Thread patrick at rivosinc dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106807 Patrick O'Neill changed: What|Removed |Added CC||patrick at rivosinc dot com --- Comme

[Bug target/106807] RISC-V: libatomic routines are infinate loops

2022-09-01 Thread palmer at gcc dot gnu.org via Gcc-bugs
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 > availab

[Bug target/106807] RISC-V: libatomic routines are infinate loops

2022-09-01 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106807 --- Comment #2 from Andreas Schwab --- For example, if configure says: checking for __atomic_fetch_add for size 1... yes but __atomic_fetch_add isn't expanded inline you will get this recursive call.

[Bug target/106807] RISC-V: libatomic routines are infinate loops

2022-09-01 Thread schwab--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106807 --- Comment #1 from Andreas Schwab --- 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.