https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117642
--- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jakub Jelinek <ja...@gcc.gnu.org>: https://gcc.gnu.org/g:4dc7a5eb6e3d49d11d9adc8085702b0bcc1540c1 commit r13-9576-g4dc7a5eb6e3d49d11d9adc8085702b0bcc1540c1 Author: Jakub Jelinek <ja...@redhat.com> Date: Thu Nov 28 14:31:44 2024 +0100 docs: Fix up __sync_* documentation [PR117642] The PR14311 commit which added support for __sync_* builtins documented that there is a warning if a particular operation cannot be implemented. But that commit nor anything later on implemented such warning, it was always silent generation of the mentioned calls (which can in most cases result in linker errors of course because those functions aren't implemented anywhere, in libatomic or elsewhere in code shipped in gcc). So, the following patch just adjust the documentation to match the implementation. 2024-11-28 Jakub Jelinek <ja...@redhat.com> PR target/117642 * doc/extend.texi: Remove documentation of warning for unimplemented __sync_* operations, such warning has never been implemented. (cherry picked from commit 0dcc09a8b5eb275ce939daad2bdfc7076ae1863c)
