This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Java,docs] Some style and link changes to gcj.texi

This updates one link ( now redirects to, remove one generic one that used to point to  And, while at it, I noticed that gcc should read GCC.

Applied to mainline; I'll probably backport to the 4.8 branch


2013-04-15  Gerald Pfeifer  <>

	* gcj.texi (Configure-time Options): Refer to GCC, not gcc.
	(Resources): Adjust reference to Mauve.
	Remove link to
	Refer to GCC, not gcc.

Index: gcj.texi
--- gcj.texi	(revision 197950)
+++ gcj.texi	(working copy)
@@ -609,7 +609,7 @@
 @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 @@
 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{}.
+Machine Specification.  In addition we've used Sun's online documentation.
 The current @command{gcj} home page is
-For more information on gcc, see @uref{}.
+For more information on GCC, see @uref{}.
 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{} for more information.
+@uref{} for more information.
 @node Index

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]