diff options
| author | Gerald Pfeifer <gerald@pfeifer.com> | 2013-04-14 21:16:58 +0000 |
|---|---|---|
| committer | Gerald Pfeifer <gerald@gcc.gnu.org> | 2013-04-14 21:16:58 +0000 |
| commit | cdbaf71ac256e7af1ea945613c8e43e572b83c72 (patch) | |
| tree | f44dd7eabbc5c680e3d263be3ea4c9183a9bb188 /gcc | |
| parent | a5e5226441e3bf95c0e0a4f4db6d687c9215229c (diff) | |
| download | gcc-cdbaf71ac256e7af1ea945613c8e43e572b83c72.zip gcc-cdbaf71ac256e7af1ea945613c8e43e572b83c72.tar.gz gcc-cdbaf71ac256e7af1ea945613c8e43e572b83c72.tar.bz2 | |
gcj.texi (Configure-time Options): Refer to GCC, not gcc.
* gcj.texi (Configure-time Options): Refer to GCC, not gcc.
(Resources): Adjust reference to Mauve.
Remove link to java.sun.com.
Refer to GCC, not gcc.
From-SVN: r197951
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/java/ChangeLog | 7 | ||||
| -rw-r--r-- | gcc/java/gcj.texi | 9 |
2 files changed, 11 insertions, 5 deletions
diff --git a/gcc/java/ChangeLog b/gcc/java/ChangeLog index f99a993..4f786b4 100644 --- a/gcc/java/ChangeLog +++ b/gcc/java/ChangeLog @@ -1,3 +1,10 @@ +2013-04-15 Gerald Pfeifer <gerald@pfeifer.com> + + * gcj.texi (Configure-time Options): Refer to GCC, not gcc. + (Resources): Adjust reference to Mauve. + Remove link to java.sun.com. + Refer to GCC, not gcc. + 2013-04-09 Richard Biener <rguenther@suse.de> * expr.c (build_java_binop): Pass a type to build_int_cst. diff --git a/gcc/java/gcj.texi b/gcc/java/gcj.texi index eaeebc7..efa24ea 100644 --- a/gcc/java/gcj.texi +++ b/gcc/java/gcj.texi @@ -609,7 +609,7 @@ 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. +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. @@ -2712,18 +2712,17 @@ While writing @command{gcj} and @code{libgcj} we have, of course, relied heavily on documentation from Sun Microsystems. In particular we have used The Java Language Specification (both first and second editions), the Java Class Libraries (volumes one and two), and the Java Virtual -Machine Specification. In addition we've used the online documentation -at @uref{http://java.sun.com/}. +Machine Specification. In addition we've used Sun's online documentation. The current @command{gcj} home page is @uref{http://gcc.gnu.org/java/}. -For more information on gcc, see @uref{http://gcc.gnu.org/}. +For more information on GCC, see @uref{http://gcc.gnu.org/}. Some @code{libgcj} testing is done using the Mauve test suite. This is a free software Java class library test suite which is being written because the JCK is not free. See -@uref{http://sources.redhat.com/mauve/} for more information. +@uref{http://www.sourceware.org/mauve/} for more information. @node Index |