aboutsummaryrefslogtreecommitdiff
path: root/gcc/expr.cc
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2024-11-28 14:31:44 +0100
committerJakub Jelinek <jakub@gcc.gnu.org>2024-11-28 14:31:44 +0100
commit0dcc09a8b5eb275ce939daad2bdfc7076ae1863c (patch)
tree6ae128e025df95349edda980e7de0c07e7c66304 /gcc/expr.cc
parent912d5cfb8cf3c2568a544a4260bac4f6f932767a (diff)
downloadgcc-0dcc09a8b5eb275ce939daad2bdfc7076ae1863c.zip
gcc-0dcc09a8b5eb275ce939daad2bdfc7076ae1863c.tar.gz
gcc-0dcc09a8b5eb275ce939daad2bdfc7076ae1863c.tar.bz2
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 <jakub@redhat.com> PR target/117642 * doc/extend.texi: Remove documentation of warning for unimplemented __sync_* operations, such warning has never been implemented.
Diffstat (limited to 'gcc/expr.cc')
0 files changed, 0 insertions, 0 deletions