aboutsummaryrefslogtreecommitdiff
path: root/gcc/java/gcj.texi
diff options
context:
space:
mode:
authorAndrew Haley <aph@redhat.com>2009-08-12 16:10:12 +0000
committerAndrew Haley <aph@gcc.gnu.org>2009-08-12 16:10:12 +0000
commit4b462d7786135d389f58ccda0a9dddf9ed4cee73 (patch)
tree2b29a3b4b734755142382ee704c64493d0a28268 /gcc/java/gcj.texi
parent97804369a99a4e9ab5609b158ce5b0becff36880 (diff)
downloadgcc-4b462d7786135d389f58ccda0a9dddf9ed4cee73.zip
gcc-4b462d7786135d389f58ccda0a9dddf9ed4cee73.tar.gz
gcc-4b462d7786135d389f58ccda0a9dddf9ed4cee73.tar.bz2
builtins.c (compareAndSwapInt_builtin): Use flag_use_atomic_builtins.
2009-08-12 Andrew Haley <aph@redhat.com> * builtins.c (compareAndSwapInt_builtin): Use flag_use_atomic_builtins. (compareAndSwapLong_builtin): Likewise. (compareAndSwapObject_builtin): Likewise. * jvspec.c: Add flag_use_atomic_builtins. * gcj.texi: Likewise. * java-tree.h: Likewise. * lang.opt: Likewise. From-SVN: r150699
Diffstat (limited to 'gcc/java/gcj.texi')
-rw-r--r--gcc/java/gcj.texi7
1 files changed, 7 insertions, 0 deletions
diff --git a/gcc/java/gcj.texi b/gcc/java/gcj.texi
index 00ac9f7..46b0899 100644
--- a/gcc/java/gcj.texi
+++ b/gcc/java/gcj.texi
@@ -607,6 +607,13 @@ On some systems it's necessary to insert inline checks whenever
accessing an object via a reference. On other systems you won't need
this because null pointer accesses are caught automatically by the
processor.
+
+@item -fuse-atomic-builtins
+On some systems, gcc can generate code for built-in atomic operations.
+Use this option to force gcj to use these builtins when compiling Java
+code. Where this capability is present it should be automatically
+detected, so you won't usually need to use this option.
+
@end table
@c man end