From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: [Java,docs] Some style and link changes to gcj.texi
Date: Sun, 14 Apr 2013 21:22:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1304150114210.1745@trevally.site> (raw)
This updates one link (sources.redhat.com now redirects to
sourceware.org), remove one generic one that used to point to
sun.com. And, while at it, I noticed that gcc should read GCC.
Applied to mainline; I'll probably backport to the 4.8 branch
later.
Gerald
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.
Index: gcj.texi
===================================================================
--- gcj.texi (revision 197950)
+++ gcj.texi (working copy)
@@ -609,7 +609,7 @@
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 @@
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
reply other threads:[~2013-04-14 21:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1304150114210.1745@trevally.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).