From: David Daney <ddaney@avtrex.com>
To: Java Patch List <java-patches@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [Patch, Doc] Java: Clarify restrictions on -freduced-reflection option.
Date: Mon, 25 Aug 2008 21:52:00 -0000 [thread overview]
Message-ID: <48B31D33.5090602@avtrex.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 251 bytes --]
This patch slightly enhances the documentation for GCJ's
-freduced-reflection option.
Tested with make info.
OK to commit?
gcc/java:
2008-08-25 David Daney <ddaney@avtrex.com>
* gcj.texi (-freduced-reflection): Clarify option's restrictions.
[-- Attachment #2: reduced-reflection-doc.patch --]
[-- Type: text/x-patch, Size: 897 bytes --]
Index: gcj.texi
===================================================================
--- gcj.texi (revision 139396)
+++ gcj.texi (working copy)
@@ -557,9 +557,10 @@ the ability to use certain reflection ca
Java runtime environment. When set all meta-data except for that
which is needed to obtain correct runtime semantics is eliminated.
-For code that does not use reflection (i.e. the methods in the
-@code{java.lang.reflect} package), @code{-freduced-reflection}
-will result in proper operation with a savings in executable code size.
+For code that does not use reflection (i.e. serialization, RMI, CORBA
+and/or call methods in the @code{java.lang.reflect} package),
+@code{-freduced-reflection} will result in proper operation with a
+savings in executable code size.
JNI (@code{-fjni}) and the binary compatibility ABI
(@code{-findirect-dispatch}) do not work properly without full
next reply other threads:[~2008-08-25 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 21:52 David Daney [this message]
2008-09-06 5:04 ` David Daney
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=48B31D33.5090602@avtrex.com \
--to=ddaney@avtrex.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).