diff options
Diffstat (limited to 'gcc/doc/gcj.1')
| -rw-r--r-- | gcc/doc/gcj.1 | 73 |
1 files changed, 36 insertions, 37 deletions
diff --git a/gcc/doc/gcj.1 b/gcc/doc/gcj.1 index e9de845c9b..69849317cd 100644 --- a/gcc/doc/gcj.1 +++ b/gcc/doc/gcj.1 @@ -1,7 +1,15 @@ -.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.29) +.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05) .\" .\" Standard preamble: .\" ======================================================================== +.de Sh \" Subsection heading +.br +.if t .Sp +.ne 5 +.PP +\fB\\$1\fR +.PP +.. .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp @@ -38,8 +46,6 @@ . ds PI \(*p . ds L" `` . ds R" '' -. ds C` -. ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. @@ -47,27 +53,20 @@ .el .ds Aq ' .\" .\" If the F register is turned on, we'll generate index entries on stderr for -.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. -.\" -.\" Avoid warning from groff about undefined register 'F'. -.de IX +.ie \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" .. -.nr rF 0 -.if \n(.g .if rF .nr rF 1 -.if (\n(rF:(\n(.g==0)) \{ -. if \nF \{ -. de IX -. tm Index:\\$1\t\\n%\t"\\$2" +. nr % 0 +. rr F +.\} +.el \{\ +. de IX .. -. if !\nF==2 \{ -. nr % 0 -. nr F 2 -. \} -. \} .\} -.rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. @@ -133,7 +132,7 @@ .\" ======================================================================== .\" .IX Title "GCJ 1" -.TH GCJ 1 "2016-04-27" "gcc-6.1.0" "GNU" +.TH GCJ 1 "2016-08-22" "gcc-6.2.0" "GNU" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l @@ -156,7 +155,7 @@ of the same options as gcc. This manual only documents the options specific to \fBgcj\fR. .SH "OPTIONS" .IX Header "OPTIONS" -.SS "Input and output files" +.Sh "Input and output files" .IX Subsection "Input and output files" A \fBgcj\fR command is like a \fBgcc\fR command, in that it consists of a number of options and file names. The following kinds @@ -204,7 +203,7 @@ but not when using \f(CW\*(C`\-C\*(C'\fR or \f(CW\*(C`\-\-resource\*(C'\fR. (This is an extension beyond the what plain \fBgcc\fR allows.) (If more than one input file is specified, all must currently be \f(CW\*(C`.java\*(C'\fR files, though we hope to fix this.) -.SS "Input Options" +.Sh "Input Options" .IX Subsection "Input Options" \&\fBgcj\fR has options to control where it looks to find files it needs. For instance, \fBgcj\fR might need to load a class that is referenced @@ -278,7 +277,7 @@ issue an error if it isn't found. .IX Item "-fsource=VERSION" This option is used to choose the source version accepted by \&\fBgcj\fR. The default is \fB1.5\fR. -.SS "Encodings" +.Sh "Encodings" .IX Subsection "Encodings" The Java programming language uses Unicode throughout. In an effort to integrate well with other locales, \fBgcj\fR allows \fI.java\fR files @@ -301,7 +300,7 @@ to platform (since they are not standardized anywhere). However, \&\fBgcj\fR implements the encoding named \fB\s-1UTF\-8\s0\fR internally, so if you choose to use this for your source files you can be assured that it will work on every host. -.SS "Warnings" +.Sh "Warnings" .IX Subsection "Warnings" \&\fBgcj\fR implements several warnings. As with other generic \&\fBgcc\fR warnings, if an option of the form \f(CW\*(C`\-Wfoo\*(C'\fR enables a @@ -331,7 +330,7 @@ This is the same as \fBgcc\fR's \f(CW\*(C`\-Wunused\*(C'\fR. .IX Item "-Wall" This is the same as \f(CW\*(C`\-Wredundant\-modifiers \-Wextraneous\-semicolon \&\-Wunused\*(C'\fR. -.SS "Linking" +.Sh "Linking" .IX Subsection "Linking" To turn a Java application into an executable program, you need to link it with the needed libraries, just as for C or \*(C+. @@ -392,7 +391,7 @@ link time, it can omit the referred to classes. The result is usually runtime. Caution must be used when using this option. For more details see: <\fBhttp://gcc.gnu.org/wiki/Statically%20linking%20libgcj\fR> -.SS "Code Generation" +.Sh "Code Generation" .IX Subsection "Code Generation" In addition to the many \fBgcc\fR options controlling code generation, \&\fBgcj\fR has several options specific to itself. @@ -440,9 +439,9 @@ It is safe to use this option if you are sure your code will never throw an .IP "\fB\-fjni\fR" 4 .IX Item "-fjni" With \fBgcj\fR there are two options for writing native methods: \s-1CNI\s0 -and \s-1JNI. \s0 By default \fBgcj\fR assumes you are using \s-1CNI. \s0 If you are +and \s-1JNI\s0. By default \fBgcj\fR assumes you are using \s-1CNI\s0. If you are compiling a class with native methods, and these methods are implemented -using \s-1JNI,\s0 then you must use \f(CW\*(C`\-fjni\*(C'\fR. This option causes +using \s-1JNI\s0, then you must use \f(CW\*(C`\-fjni\*(C'\fR. This option causes \&\fBgcj\fR to generate stubs which will invoke the underlying \s-1JNI\s0 methods. .IP "\fB\-fno\-assert\fR" 4 @@ -479,7 +478,7 @@ So this flag isn't very useful yet, except to partially override \&\f(CW\*(C`\-\-disable\-assertions\*(C'\fR. .IP "\fB\-findirect\-dispatch\fR" 4 .IX Item "-findirect-dispatch" -\&\fBgcj\fR has a special binary compatibility \s-1ABI,\s0 which is enabled +\&\fBgcj\fR has a special binary compatibility \s-1ABI\s0, which is enabled by the \f(CW\*(C`\-findirect\-dispatch\*(C'\fR option. In this mode, the code generated by \fBgcj\fR honors the binary compatibility guarantees in the Java Language Specification, and the resulting object files do @@ -490,10 +489,10 @@ interpreted and compiled code. Note that, at present, \f(CW\*(C`\-findirect\-dispatch\*(C'\fR can only be used when compiling \fI.class\fR files. It will not work when compiling from source. \s-1CNI\s0 also does not yet work with the binary compatibility -\&\s-1ABI. \s0 These restrictions will be lifted in some future release. +\&\s-1ABI\s0. These restrictions will be lifted in some future release. .Sp -However, if you compile \s-1CNI\s0 code with the standard \s-1ABI,\s0 you can call -it from code built with the binary compatibility \s-1ABI.\s0 +However, if you compile \s-1CNI\s0 code with the standard \s-1ABI\s0, you can call +it from code built with the binary compatibility \s-1ABI\s0. .IP "\fB\-fbootstrap\-classes\fR" 4 .IX Item "-fbootstrap-classes" This option can be use to tell \f(CW\*(C`libgcj\*(C'\fR that the compiled classes @@ -512,13 +511,13 @@ the ability to use certain reflection capabilities of the standard Java runtime environment. When set all meta-data except for that which is needed to obtain correct runtime semantics is eliminated. .Sp -For code that does not use reflection (i.e. serialization, \s-1RMI, CORBA\s0 +For code that does not use reflection (i.e. serialization, \s-1RMI\s0, \s-1CORBA\s0 or call methods in the \f(CW\*(C`java.lang.reflect\*(C'\fR package), \&\f(CW\*(C`\-freduced\-reflection\*(C'\fR will result in proper operation with a savings in executable code size. .Sp -\&\s-1JNI \s0(\f(CW\*(C`\-fjni\*(C'\fR) and the binary compatibility \s-1ABI -\&\s0(\f(CW\*(C`\-findirect\-dispatch\*(C'\fR) do not work properly without full +\&\s-1JNI\s0 (\f(CW\*(C`\-fjni\*(C'\fR) and the binary compatibility \s-1ABI\s0 +(\f(CW\*(C`\-findirect\-dispatch\*(C'\fR) do not work properly without full reflection meta-data. Because of this, it is an error to use these options with \f(CW\*(C`\-freduced\-reflection\*(C'\fR. .Sp @@ -526,9 +525,9 @@ with \f(CW\*(C`\-freduced\-reflection\*(C'\fR. a \f(CW\*(C`SecurityManager\*(C'\fR may not work properly. Also calling \&\f(CW\*(C`Class.forName()\*(C'\fR may fail if the calling method has no reflection meta-data. -.SS "Configure-time Options" +.Sh "Configure-time Options" .IX Subsection "Configure-time Options" -Some \fBgcj\fR code generations options affect the resulting \s-1ABI,\s0 and +Some \fBgcj\fR code generations options affect the resulting \s-1ABI\s0, and so can only be meaningfully given when \f(CW\*(C`libgcj\*(C'\fR, the runtime package, is configured. \f(CW\*(C`libgcj\*(C'\fR puts the appropriate options from this group into a \fBspec\fR file which is read by \fBgcj\fR. These |