Commit cdbaf71a by Gerald Pfeifer Committed by Gerald Pfeifer

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
parent a5e52264
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> 2013-04-09 Richard Biener <rguenther@suse.de>
* expr.c (build_java_binop): Pass a type to build_int_cst. * expr.c (build_java_binop): Pass a type to build_int_cst.
......
...@@ -609,7 +609,7 @@ this because null pointer accesses are caught automatically by the ...@@ -609,7 +609,7 @@ this because null pointer accesses are caught automatically by the
processor. processor.
@item -fuse-atomic-builtins @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 Use this option to force gcj to use these builtins when compiling Java
code. Where this capability is present it should be automatically code. Where this capability is present it should be automatically
detected, so you won't usually need to use this option. 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 ...@@ -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 heavily on documentation from Sun Microsystems. In particular we have
used The Java Language Specification (both first and second editions), used The Java Language Specification (both first and second editions),
the Java Class Libraries (volumes one and two), and the Java Virtual the Java Class Libraries (volumes one and two), and the Java Virtual
Machine Specification. In addition we've used the online documentation Machine Specification. In addition we've used Sun's online documentation.
at @uref{http://java.sun.com/}.
The current @command{gcj} home page is The current @command{gcj} home page is
@uref{http://gcc.gnu.org/java/}. @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 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 a free software Java class library test suite which is being written
because the JCK is not free. See 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 @node Index
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment