This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
[PATCH] Texinfo formatting improvements
- From: Di-an JAN <dianj at sdf dot lonestar dot org>
- To: gcc-patches at gcc dot gnu dot org
- Cc: java-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Mon, 1 Nov 2004 07:29:10 -0800 (PST)
- Subject: [PATCH] Texinfo formatting improvements
This is an obvious patch to improvement Texinfo documentation by
marking @code/@option/@file/@samp and using TeX quotes and dashes.
I also removed an extraneous 'o' character and hyphenated Tree-SSA.
Tested along with my next doc patch with 'make info' and 'make dvi'.
Please apply if approved. I do not have CVS write access.
I would like to file copyright assignment just in case.
Can I use the process in
http://gcc.gnu.org/ml/gcc/2003-06/msg02298.html
Di-an Jan
[gcc/ChangeLog]
2004-11-01 Di-an Jan <dianj@freeshell.org>
* doc/cpp.texi, doc/extend.texi, doc/gcov.texi, doc/invoke.texi,
doc/passes.texi, doc/tm.texi: Use Texinfo markups.
* doc/passes.texi (Redundant phi elimination): Remove extraneous o.
[gcc/fortran/ChangeLog]
2004-11-01 Di-an Jan <dianj@freeshell.org>
* gfortran.texi: Use Texinfo markups.
[gcc/java/ChangeLog]
2004-11-01 Di-an Jan <dianj@freeshell.org>
* gcj.texi: Use Texinfo markups.
[gcc/treelang/ChangeLog]
2004-11-01 Di-an Jan <dianj@freeshell.org>
* treelang.texi: Use Texinfo markups. Hyphenate Tree-SSA.
Index: gcc/doc/cpp.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/doc/cpp.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 cpp.texi
*** gcc/doc/cpp.texi 30 Oct 2004 16:45:38 -0000 1.1.1.1
--- gcc/doc/cpp.texi 30 Oct 2004 19:10:28 -0000
*************** @node Differences from previous versions
*** 4046,4052 ****
@itemize @bullet
! @item -I- deprecated
This option has been deprecated in 3.5. @option{-iquote} is meant to
replace the need for this option.
--- 4046,4052 ----
@itemize @bullet
! @item @option{-I-} deprecated
This option has been deprecated in 3.5. @option{-iquote} is meant to
replace the need for this option.
Index: gcc/doc/extend.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/doc/extend.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 extend.texi
*** gcc/doc/extend.texi 30 Oct 2004 16:45:39 -0000 1.1.1.1
--- gcc/doc/extend.texi 30 Oct 2004 19:10:28 -0000
*************** @node Zero Length
*** 868,875 ****
cases that were useful, it also allowed initializations in situations
that would corrupt later data. Non-empty initialization of zero-length
arrays is now treated like any case where there are more initializer
! elements than the array holds, in that a suitable warning about "excess
! elements in array" is given, and the excess elements (all of them, in
this case) are ignored.
Instead GCC allows static initialization of flexible array members.
--- 868,875 ----
cases that were useful, it also allowed initializations in situations
that would corrupt later data. Non-empty initialization of zero-length
arrays is now treated like any case where there are more initializer
! elements than the array holds, in that a suitable warning about ``excess
! elements in array'' is given, and the excess elements (all of them, in
this case) are ignored.
Instead GCC allows static initialization of flexible array members.
Index: gcc/doc/gcov.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/doc/gcov.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 gcov.texi
*** gcc/doc/gcov.texi 30 Oct 2004 16:45:39 -0000 1.1.1.1
--- gcc/doc/gcov.texi 30 Oct 2004 19:10:28 -0000
*************** @node Invoking Gcov
*** 331,337 ****
-: 17:@}
@end smallexample
! In this mode, each basic block is only shown on one line -- the last
line of the block. A multi-line block will only contribute to the
execution count of that last line, and other lines will not be shown
to contain code, unless previous blocks end on those lines.
--- 331,337 ----
-: 17:@}
@end smallexample
! In this mode, each basic block is only shown on one line---the last
line of the block. A multi-line block will only contribute to the
execution count of that last line, and other lines will not be shown
to contain code, unless previous blocks end on those lines.
Index: gcc/doc/invoke.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 invoke.texi
*** gcc/doc/invoke.texi 30 Oct 2004 16:45:39 -0000 1.1.1.1
--- gcc/doc/invoke.texi 30 Oct 2004 20:41:58 -0000
*************** @node Optimize Options
*** 5554,5560 ****
generation.
The default is 30% + 70% * (RAM/1GB) with an upper bound of 100% when
! RAM >= 1GB. If @code{getrlimit} is available, the notion of "RAM" is
the smallest of actual RAM and RLIMIT_DATA or RLIMIT_AS. If
GCC is not able to calculate RAM on a particular platform, the lower
bound of 30% is used. Setting this parameter and
--- 5554,5560 ----
generation.
The default is 30% + 70% * (RAM/1GB) with an upper bound of 100% when
! RAM >= 1GB. If @code{getrlimit} is available, the notion of ``RAM'' is
the smallest of actual RAM and RLIMIT_DATA or RLIMIT_AS. If
GCC is not able to calculate RAM on a particular platform, the lower
bound of 30% is used. Setting this parameter and
Index: gcc/doc/passes.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/doc/passes.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 passes.texi
*** gcc/doc/passes.texi 30 Oct 2004 16:45:39 -0000 1.1.1.1
--- gcc/doc/passes.texi 30 Oct 2004 20:41:58 -0000
*************** @node Parsing pass
*** 63,69 ****
only be invoked when it is certain that the outer-most function
is used.
! TODO: Cgraph needs a gimplify_function callback. It should be
invoked when (1) it is certain that the function is used, (2)
warning flags specified by the user require some amount of
compilation in order to honor, (3) the language indicates that
--- 63,69 ----
only be invoked when it is certain that the outer-most function
is used.
! TODO: Cgraph needs a @code{gimplify_function} callback. It should be
invoked when (1) it is certain that the function is used, (2)
warning flags specified by the user require some amount of
compilation in order to honor, (3) the language indicates that
*************** @node Parsing pass
*** 92,104 ****
be passed to @code{rest_of_type_compilation}. Each function definition
should be passed to @code{cgraph_finalize_function}.
! TODO: I know rest_of_compilation currently has all sorts of
rtl-generation semantics. I plan to move all code generation
! bits (both tree and rtl) to compile_function. Should we hide
! cgraph from the front ends and move back to rest_of_compilation
as the official interface? Possibly we should rename all three
interfaces such that the names match in some meaningful way and
! that is more descriptive than "rest_of".
The middle-end will, at its option, emit the function and data
definitions immediately or queue them for later processing.
--- 92,104 ----
be passed to @code{rest_of_type_compilation}. Each function definition
should be passed to @code{cgraph_finalize_function}.
! TODO: I know @code{rest_of_compilation} currently has all sorts of
rtl-generation semantics. I plan to move all code generation
! bits (both tree and rtl) to @code{compile_function}. Should we hide
! cgraph from the front ends and move back to @code{rest_of_compilation}
as the official interface? Possibly we should rename all three
interfaces such that the names match in some meaningful way and
! that is more descriptive than ``rest_of.''
The middle-end will, at its option, emit the function and data
definitions immediately or queue them for later processing.
*************** @node Tree-SSA passes
*** 281,287 ****
value, excluding feedback. Such degenerate forms are typically created
by removing unreachable code. The pass is run multiple times throughout
the optimization process. It is located in @file{tree-ssa.c} and is
! described by @code{pass_redundant_phi}.o
@item Forward propagation of single-use variables
--- 281,287 ----
value, excluding feedback. Such degenerate forms are typically created
by removing unreachable code. The pass is run multiple times throughout
the optimization process. It is located in @file{tree-ssa.c} and is
! described by @code{pass_redundant_phi}.
@item Forward propagation of single-use variables
*************** @node Tree-SSA passes
*** 398,404 ****
We identify if convertable loops, if-convert statements and merge
basic blocks in one big block. The idea is to present loop in such
form so that vectorizer can have one to one mapping between statements
! and available vector operations. This patch re-introduces COND_EXPR
at GIMPLE level. This pass is located in @file{tree-if-conv.c}.
@item Conditional constant propagation
--- 398,404 ----
We identify if convertable loops, if-convert statements and merge
basic blocks in one big block. The idea is to present loop in such
form so that vectorizer can have one to one mapping between statements
! and available vector operations. This patch re-introduces @code{COND_EXPR}
at GIMPLE level. This pass is located in @file{tree-if-conv.c}.
@item Conditional constant propagation
Index: gcc/doc/tm.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/doc/tm.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 tm.texi
*** gcc/doc/tm.texi 30 Oct 2004 16:45:38 -0000 1.1.1.1
--- gcc/doc/tm.texi 30 Oct 2004 20:41:58 -0000
*************** @node Driver
*** 150,157 ****
second of which is a space-separated (tabs and other whitespace are not
supported) list of options with which to replace the first option. The
target defining this list is responsible for assuring that the results
! are valid. Replacement options may not be the @code{--opt} style, they
! must be the @code{-opt} style. It is the intention of this macro to
provide a mechanism for substitution that affects the multilibs chosen,
such as one option that enables many options, some of which select
multilibs. Example nonsensical definition, where @option{-malt-abi},
--- 150,157 ----
second of which is a space-separated (tabs and other whitespace are not
supported) list of options with which to replace the first option. The
target defining this list is responsible for assuring that the results
! are valid. Replacement options may not be the @option{--@var{opt}} style, they
! must be the @option{-@var{opt}} style. It is the intention of this macro to
provide a mechanism for substitution that affects the multilibs chosen,
such as one option that enables many options, some of which select
multilibs. Example nonsensical definition, where @option{-malt-abi},
*************** @node Driver
*** 309,317 ****
@defmac USE_LD_AS_NEEDED
A macro that controls the modifications to @code{LIBGCC_SPEC}
mentioned in @code{REAL_LIBGCC_SPEC}. If nonzero, a spec will be
! generated that uses --as-needed and the shared libgcc in place of the
static exception handler library, when linking without any of
! @code{-static}, @code{-static-libgcc}, or @code{-shared-libgcc}.
@end defmac
@defmac LINK_EH_SPEC
--- 309,317 ----
@defmac USE_LD_AS_NEEDED
A macro that controls the modifications to @code{LIBGCC_SPEC}
mentioned in @code{REAL_LIBGCC_SPEC}. If nonzero, a spec will be
! generated that uses @option{--as-needed} and the shared @file{libgcc} in place of the
static exception handler library, when linking without any of
! @option{-static}, @option{-static-libgcc}, or @option{-shared-libgcc}.
@end defmac
@defmac LINK_EH_SPEC
*************** @node Driver
*** 430,436 ****
@end defmac
@defmac LINK_GCC_C_SEQUENCE_SPEC
! The sequence in which libgcc and libc are specified to the linker.
By default this is @code{%G %L %G}.
@end defmac
--- 430,436 ----
@end defmac
@defmac LINK_GCC_C_SEQUENCE_SPEC
! The sequence in which @file{libgcc} and @file{libc} are specified to the linker.
By default this is @code{%G %L %G}.
@end defmac
*************** @node Storage Layout
*** 1073,1079 ****
A C expression whose value is greater than zero if pointers that need to be
extended from being @code{POINTER_SIZE} bits wide to @code{Pmode} are to
be zero-extended and zero if they are to be sign-extended. If the value
! is less then zero then there must be an "ptr_extend" instruction that
extends a pointer from @code{POINTER_SIZE} to @code{Pmode}.
You need not define this macro if the @code{POINTER_SIZE} is equal
--- 1073,1079 ----
A C expression whose value is greater than zero if pointers that need to be
extended from being @code{POINTER_SIZE} bits wide to @code{Pmode} are to
be zero-extended and zero if they are to be sign-extended. If the value
! is less then zero then there must be an @code{ptr_extend} instruction that
extends a pointer from @code{POINTER_SIZE} to @code{Pmode}.
You need not define this macro if the @code{POINTER_SIZE} is equal
*************** @node Register Arguments
*** 3884,3890 ****
macro allows better control of register function parameters on big-endian
machines, without using @code{PARALLEL} rtl. In particular,
@code{MUST_PASS_IN_STACK} need not test padding and mode of types in
! registers, as there is no longer a "wrong" part of a register; For example,
a three byte aggregate may be passed in the high part of a register if so
required.
@end defmac
--- 3884,3890 ----
macro allows better control of register function parameters on big-endian
machines, without using @code{PARALLEL} rtl. In particular,
@code{MUST_PASS_IN_STACK} need not test padding and mode of types in
! registers, as there is no longer a ``wrong'' part of a register; For example,
a three byte aggregate may be passed in the high part of a register if so
required.
@end defmac
*************** @node Function Entry
*** 4276,4283 ****
and epilogue later in the game than usual, namely after all passes that
modify the instructions (and not merely reorder them) have been run. In
particular, the C variable @code{current_function_uses_only_leaf_regs} is
! valid at that point. This can be used on machines that have "register
! windows" to optimize away the regular "push" on the register stack.
@xref{Leaf Functions}.
@end deftypefn
--- 4276,4283 ----
and epilogue later in the game than usual, namely after all passes that
modify the instructions (and not merely reorder them) have been run. In
particular, the C variable @code{current_function_uses_only_leaf_regs} is
! valid at that point. This can be used on machines that have ``register
! windows'' to optimize away the regular ``push'' on the register stack.
@xref{Leaf Functions}.
@end deftypefn
*************** @node Library Calls
*** 4796,4802 ****
@defmac DECLARE_LIBRARY_RENAMES
This macro, if defined, should expand to a piece of C code that will get
! expanded when compiling functions for libgcc.a. It can be used to
provide alternate names for GCC's internal library functions if there
are ABI-mandated names that the compiler should provide.
@end defmac
--- 4796,4802 ----
@defmac DECLARE_LIBRARY_RENAMES
This macro, if defined, should expand to a piece of C code that will get
! expanded when compiling functions for @file{libgcc.a}. It can be used to
provide alternate names for GCC's internal library functions if there
are ABI-mandated names that the compiler should provide.
@end defmac
*************** @node Scheduling
*** 5830,5836 ****
that will be formed, and (c) correctly emulating the grouping can be very
important. In such targets one may want to allow issuing dependent insns
closer to one another---i.e., closer than the dependence distance; however,
! not in cases of "costly dependences", which this hooks allows to define.
@end deftypefn
Macros in the following table are generated by the program
--- 5830,5836 ----
that will be formed, and (c) correctly emulating the grouping can be very
important. In such targets one may want to allow issuing dependent insns
closer to one another---i.e., closer than the dependence distance; however,
! not in cases of ``costly dependences,'' which this hooks allows to define.
@end deftypefn
Macros in the following table are generated by the program
*************** @node File Framework
*** 6283,6289 ****
is nonzero, it contains an alignment in bytes to be used for the section,
otherwise some target default should be used. Only targets that must
specify an alignment within the section directive need pay attention to
! @var{align} -- we will still use @code{ASM_OUTPUT_ALIGN}.
@end deftypefn
@deftypefn {Target Hook} bool TARGET_HAVE_NAMED_SECTIONS
--- 6283,6289 ----
is nonzero, it contains an alignment in bytes to be used for the section,
otherwise some target default should be used. Only targets that must
specify an alignment within the section directive need pay attention to
! @var{align}---we will still use @code{ASM_OUTPUT_ALIGN}.
@end deftypefn
@deftypefn {Target Hook} bool TARGET_HAVE_NAMED_SECTIONS
*************** @node Misc
*** 9114,9120 ****
the behavior to the default.
A subtlety for Microsoft Visual C/C++ style bit-field packing
! (e.g.@: -mms-bitfields) for targets that support it:
When a bit-field is inserted into a packed record, the whole size
of the underlying type is used by one or more same-size adjacent
bit-fields (that is, if its long:3, 32 bits is used in the record,
--- 9114,9120 ----
the behavior to the default.
A subtlety for Microsoft Visual C/C++ style bit-field packing
! (e.g.@: @option{-mms-bitfields}) for targets that support it:
When a bit-field is inserted into a packed record, the whole size
of the underlying type is used by one or more same-size adjacent
bit-fields (that is, if its long:3, 32 bits is used in the record,
Index: gcc/fortran/gfortran.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/fortran/gfortran.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 gfortran.texi
*** gcc/fortran/gfortran.texi 30 Oct 2004 16:45:40 -0000 1.1.1.1
--- gcc/fortran/gfortran.texi 30 Oct 2004 19:10:28 -0000
*************** @node Compiler Status
*** 420,426 ****
(PARAMETER variables) and reads and generate module files. This is
almost complete. Every Fortran 95 source should be accepted, and most
none-Fortran 95 source should be rejected. If you find a source file where
! this is not true, please tell us. You can use the -fsyntax-only switch to
make gfortran quit after running the front end, effectively reducing it to
a syntax checker.
--- 420,426 ----
(PARAMETER variables) and reads and generate module files. This is
almost complete. Every Fortran 95 source should be accepted, and most
none-Fortran 95 source should be rejected. If you find a source file where
! this is not true, please tell us. You can use the @option{-fsyntax-only} switch to
make gfortran quit after running the front end, effectively reducing it to
a syntax checker.
*************** @node Proposed Extensions
*** 509,515 ****
character to ``C''-style escape characters.
@item
! Compile flag to generate code for array conformance checking (suggest -CC).
@item
User control of symbol names (underscores, etc).
--- 509,515 ----
character to ``C''-style escape characters.
@item
! Compile flag to generate code for array conformance checking (suggest @option{-CC}).
@item
User control of symbol names (underscores, etc).
*************** @node Proposed Extensions
*** 534,540 ****
Flag for maximum errors before ending compile.
@item
! Generate code to check for null pointer dereferences -- prints locus of
dereference instead of segfaulting. There was some discussion about this
option in the g95 development mailing list.
--- 534,540 ----
Flag for maximum errors before ending compile.
@item
! Generate code to check for null pointer dereferences---prints locus of
dereference instead of segfaulting. There was some discussion about this
option in the g95 development mailing list.
*************** @node Proposed Extensions
*** 564,570 ****
@item
Environment variables controlling actions on arithmetic exceptions like
! overflow, underflow, precision loss -- Generate NaN, abort, default.
action.
@item
--- 564,570 ----
@item
Environment variables controlling actions on arithmetic exceptions like
! overflow, underflow, precision loss---Generate NaN, abort, default.
action.
@item
Index: gcc/java/gcj.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/java/gcj.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 gcj.texi
*** gcc/java/gcj.texi 30 Oct 2004 16:45:42 -0000 1.1.1.1
--- gcc/java/gcj.texi 30 Oct 2004 20:41:58 -0000
*************** @node Warnings
*** 325,331 ****
@command{gcj} implements several warnings. As with other generic
@command{gcc} warnings, if an option of the form @code{-Wfoo} enables a
warning, then @code{-Wno-foo} will disable it. Here we've chosen to
! document the form of the warning which will have an effect -- the
default being the opposite of what is listed.
@table @gcctabopt
--- 325,331 ----
@command{gcj} implements several warnings. As with other generic
@command{gcc} warnings, if an option of the form @code{-Wfoo} enables a
warning, then @code{-Wno-foo} will disable it. Here we've chosen to
! document the form of the warning which will have an effect---the
default being the opposite of what is listed.
@table @gcctabopt
*************** @node Mixing with C++
*** 1868,1874 ****
@code{gnu.gcj.RawDataManaged} is another type used to indicate special data used
by native code. Unlike the @code{RawData} type, fields declared as
! @code{RawDataManaged} will be "marked" by the memory manager and
considered for garbage collection.
Native data which is allocated using CNI's @code{JvAllocBytes()}
--- 1868,1874 ----
@code{gnu.gcj.RawDataManaged} is another type used to indicate special data used
by native code. Unlike the @code{RawData} type, fields declared as
! @code{RawDataManaged} will be ``marked'' by the memory manager and
considered for garbage collection.
Native data which is allocated using CNI's @code{JvAllocBytes()}
Index: gcc/treelang/treelang.texi
===================================================================
RCS file: /e/cvs/gcc/gcc/treelang/treelang.texi,v
retrieving revision 1.1.1.1
diff -c -3 -F@node -r1.1.1.1 treelang.texi
*** gcc/treelang/treelang.texi 30 Oct 2004 16:47:28 -0000 1.1.1.1
--- gcc/treelang/treelang.texi 30 Oct 2004 20:43:28 -0000
***************
*** 132,138 ****
@end ifnottex
treelang was Contributed by Tim Josling (@email{@value{email-josling}}).
! Inspired by and based on the 'toy' language, written by Richard Kenner.
This document was written by Tim Josling, based on the GNU C++
documentation.
--- 132,138 ----
@end ifnottex
treelang was Contributed by Tim Josling (@email{@value{email-josling}}).
! Inspired by and based on the ``toy'' language, written by Richard Kenner.
This document was written by Tim Josling, based on the GNU C++
documentation.
*************** @node Contributors
*** 263,273 ****
@cindex contributors
@cindex credits
! Treelang was based on 'toy' by Richard Kenner, and also uses code from
the GCC core code tree. Tim Josling first created the language and
documentation, based on the GCC Fortran compiler's documentation
! framework. Treelang was updated to use the TreeSSA infrastructure by James A.
! Morrison.
@itemize @bullet
@item
--- 263,273 ----
@cindex contributors
@cindex credits
! Treelang was based on ``toy'' by Richard Kenner, and also uses code from
the GCC core code tree. Tim Josling first created the language and
documentation, based on the GCC Fortran compiler's documentation
! framework. Treelang was updated to use the Tree-SSA infrastructure by
! James A. Morrison.
@itemize @bullet
@item
*************** @node What is GNU Treelang?, Lexical Syn
*** 328,334 ****
@cindex basic concepts
GNU Treelang, or @code{treelang}, is designed initially as a free
! replacement for, or alternative to, the 'toy' language, but which is
amenable to inclusion within the GCC source tree.
@code{treelang} is largely a cut down version of C, designed to showcase
--- 328,334 ----
@cindex basic concepts
GNU Treelang, or @code{treelang}, is designed initially as a free
! replacement for, or alternative to, the ``toy'' language, but which is
amenable to inclusion within the GCC source tree.
@code{treelang} is largely a cut down version of C, designed to showcase
*************** @node Lexical Syntax, Parsing Syntax, Wh
*** 402,409 ****
Whitespace consists of the space character, a tab, and the end of line
character. Line terminations are as defined by the
standard C library. Whitespace is ignored except within comments,
! and where it separates parts of the program. In the example below, A and
! B are two separate names separated by whitespace.
@smallexample
A B
--- 402,409 ----
Whitespace consists of the space character, a tab, and the end of line
character. Line terminations are as defined by the
standard C library. Whitespace is ignored except within comments,
! and where it separates parts of the program. In the example below,
! @samp{A} and @samp{B} are two separate names separated by whitespace.
@smallexample
A B
*************** @node Lexical Syntax, Parsing Syntax, Wh
*** 411,417 ****
@item
Comments consist of @samp{//} followed by any characters up to the end
! of the line. C style comments (/* */) are not supported. For example,
the assignment below is followed by a not very helpful comment.
@smallexample
--- 411,417 ----
@item
Comments consist of @samp{//} followed by any characters up to the end
! of the line. C style comments (@samp{/* */}) are not supported. For example,
the assignment below is followed by a not very helpful comment.
@smallexample
*************** @node Lexical Syntax, Parsing Syntax, Wh
*** 446,452 ****
@item if
begin IF statement
@item else
! begin 'else' portion of IF statement
@item static
indicate variable is permanent, or function has file scope only
@item automatic
--- 446,452 ----
@item if
begin IF statement
@item else
! begin ``else'' portion of IF statement
@item static
indicate variable is permanent, or function has file scope only
@item automatic
*************** @node treelang files, treelang compiler
*** 1032,1038 ****
lang-specs. This file is also included in GCC.c. It tells GCC.c when to
call your programs and what options to send them. The mini-language
'specs' is documented in the source of GCC.c. Do not attempt to write a
! specs file from scratch - use an existing one as the base and enhance
it.
@item
--- 1032,1038 ----
lang-specs. This file is also included in GCC.c. It tells GCC.c when to
call your programs and what options to send them. The mini-language
'specs' is documented in the source of GCC.c. Do not attempt to write a
! specs file from scratch---use an existing one as the base and enhance
it.
@item
*************** @node Open Questions, Bugs, treelang int
*** 1246,1252 ****
@chapter Open Questions
If you know GCC well, please consider looking at the file treetree.c and
! resolving any questions marked "???".
@node Bugs, Service, Open Questions, Top
@chapter Reporting Bugs
--- 1246,1252 ----
@chapter Open Questions
If you know GCC well, please consider looking at the file treetree.c and
! resolving any questions marked @samp{???}.
@node Bugs, Service, Open Questions, Top
@chapter Reporting Bugs