mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-03-10 06:16:49 +08:00
re PR other/14474 (make dvi breaks for "TeX (Web2C 7.3.1) 3.14159")
PR other/14474 * doc/md.texi (Pattern Ordering, Dependent Patterns) (Jump Patterns, Looping Patterns): Wrap in separate "@ifset INTERNALS". From-SVN: r79210
This commit is contained in:
parent
e373cdb46c
commit
a5249a214a
@ -1,3 +1,10 @@
|
||||
2004-03-10 Hans-Peter Nilsson <hp@axis.com>
|
||||
|
||||
PR other/14474
|
||||
* doc/md.texi (Pattern Ordering, Dependent Patterns)
|
||||
(Jump Patterns, Looping Patterns): Wrap in separate "@ifset
|
||||
INTERNALS".
|
||||
|
||||
2004-03-09 Zack Weinberg <zack@codesourcery.com>
|
||||
|
||||
* config/ia64/hpux.h (MULTILIB_DEFAULTS): Define.
|
||||
|
@ -3483,6 +3483,12 @@ the values of operands 1 and 2.
|
||||
|
||||
@end table
|
||||
|
||||
@end ifset
|
||||
@c Each of the following nodes are wrapped in separate
|
||||
@c "@ifset INTERNALS" to work around memory limits for the default
|
||||
@c configuration in older tetex distributions. Known to not work:
|
||||
@c tetex-1.0.7, known to work: tetex-2.0.2.
|
||||
@ifset INTERNALS
|
||||
@node Pattern Ordering
|
||||
@section When the Order of Patterns Matters
|
||||
@cindex Pattern Ordering
|
||||
@ -3506,6 +3512,8 @@ Instead of using this pattern ordering it would be possible to make the
|
||||
pattern for convert-a-byte smart enough to deal properly with any
|
||||
constant value.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Dependent Patterns
|
||||
@section Interdependence of Patterns
|
||||
@cindex Dependent Patterns
|
||||
@ -3586,6 +3594,8 @@ instructions. Instead, they should be generated from the same pattern
|
||||
that supports register-register add insns by examining the operands and
|
||||
generating the appropriate machine instruction.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Jump Patterns
|
||||
@section Defining Jump Instruction Patterns
|
||||
@cindex jump instruction patterns
|
||||
@ -3699,6 +3709,8 @@ discussed above, we have the pattern
|
||||
The @code{SELECT_CC_MODE} macro on the SPARC returns @code{CC_NOOVmode}
|
||||
for comparisons whose argument is a @code{plus}.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Looping Patterns
|
||||
@section Defining Looping Instruction Patterns
|
||||
@cindex looping instruction patterns
|
||||
@ -3804,6 +3816,8 @@ be derived from it), however, in many cases the loop induction variable
|
||||
may become redundant and removed by the flow pass.
|
||||
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Insn Canonicalizations
|
||||
@section Canonicalization of Instructions
|
||||
@cindex canonicalization of instructions
|
||||
@ -3938,6 +3952,8 @@ will be written using @code{zero_extract} rather than the equivalent
|
||||
|
||||
@end itemize
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Expander Definitions
|
||||
@section Defining RTL Sequences for Code Generation
|
||||
@cindex expander definitions
|
||||
@ -4155,6 +4171,8 @@ at the end, emit an insn to copy the result of the operation into
|
||||
itself. Such an insn will generate no code, but it can avoid problems
|
||||
in the compiler.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Insn Splitting
|
||||
@section Defining How to Split Instructions
|
||||
@cindex insn splitting
|
||||
@ -4388,6 +4406,8 @@ functionality as two separate @code{define_insn} and @code{define_split}
|
||||
patterns. It exists for compactness, and as a maintenance tool to prevent
|
||||
having to ensure the two patterns' templates match.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Including Patterns
|
||||
@section Including Patterns in Machine Descriptions.
|
||||
@cindex insn includes
|
||||
@ -4462,6 +4482,8 @@ one @option{-I} option, the directories are scanned in left-to-right
|
||||
order; the standard default directory come after.
|
||||
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Peephole Definitions
|
||||
@section Machine-Specific Peephole Optimizers
|
||||
@cindex peephole optimizer definitions
|
||||
@ -4492,6 +4514,8 @@ targets that do scheduling.
|
||||
* define_peephole2:: RTL to RTL Peephole Optimizers
|
||||
@end menu
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node define_peephole
|
||||
@subsection RTL to Text Peephole Optimizers
|
||||
@findex define_peephole
|
||||
@ -4683,6 +4707,8 @@ then the way to mention this insn in a peephole is as follows:
|
||||
@dots{})
|
||||
@end smallexample
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node define_peephole2
|
||||
@subsection RTL to RTL Peephole Optimizers
|
||||
@findex define_peephole2
|
||||
@ -4768,6 +4794,8 @@ If we had not added the @code{(match_dup 4)} in the middle of the input
|
||||
sequence, it might have been the case that the register we chose at the
|
||||
beginning of the sequence is killed by the first or second @code{set}.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Insn Attributes
|
||||
@section Instruction Attributes
|
||||
@cindex insn attributes
|
||||
@ -4791,6 +4819,8 @@ to track the condition codes.
|
||||
* Processor pipeline description:: Specifying information for insn scheduling.
|
||||
@end menu
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Defining Attributes
|
||||
@subsection Defining Attributes and their Values
|
||||
@cindex defining attributes and their values
|
||||
@ -4855,6 +4885,8 @@ If the attribute takes numeric values, no @code{enum} type will be
|
||||
defined and the function to obtain the attribute's value will return
|
||||
@code{int}.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Expressions
|
||||
@subsection Attribute Expressions
|
||||
@cindex attribute expressions
|
||||
@ -5064,6 +5096,8 @@ for numeric attributes, as @code{eq_attr} and @code{attr_flag}
|
||||
produce more efficient code for non-numeric attributes.
|
||||
@end table
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Tagging Insns
|
||||
@subsection Assigning Attribute Values to Insns
|
||||
@cindex tagging insns
|
||||
@ -5169,6 +5203,8 @@ string. Therefore, the value of the @code{length} attribute specified
|
||||
in a @code{define_asm_attributes} should be the maximum possible length
|
||||
of a single machine instruction.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Attr Example
|
||||
@subsection Example of Attribute Specifications
|
||||
@cindex attribute specifications example
|
||||
@ -5224,6 +5260,8 @@ performed on quantities smaller than a machine word clobber the condition
|
||||
code since they will set the condition code to a value corresponding to the
|
||||
full-word result.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Insn Lengths
|
||||
@subsection Computing the Length of an Insn
|
||||
@cindex insn lengths, computing
|
||||
@ -5308,6 +5346,8 @@ as follows:
|
||||
(const_int 6)))])
|
||||
@end smallexample
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Constant Attributes
|
||||
@subsection Constant Attributes
|
||||
@cindex constant attributes
|
||||
@ -5337,6 +5377,8 @@ the value of a constant attribute may use the @code{symbol_ref} form,
|
||||
but may not use either the @code{match_operand} form or @code{eq_attr}
|
||||
forms involving insn attributes.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Delay Slots
|
||||
@subsection Delay Slot Scheduling
|
||||
@cindex delay slots, defining
|
||||
@ -5412,6 +5454,8 @@ branch is true, we might represent this as follows:
|
||||
@end smallexample
|
||||
@c the above is *still* too long. --mew 4feb93
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Processor pipeline description
|
||||
@subsection Specifying processor pipeline description
|
||||
@cindex processor pipeline description
|
||||
@ -5497,6 +5541,8 @@ choose the best one.
|
||||
* Comparison of the two descriptions:: Drawbacks of the old pipeline description
|
||||
@end menu
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Old pipeline description
|
||||
@subsubsection Specifying Function Units
|
||||
@cindex old pipeline description
|
||||
@ -5619,6 +5665,8 @@ used during their execution and there is no way of representing that
|
||||
conflict. We welcome any examples of how function unit conflicts work
|
||||
in such processors and suggestions for their representation.
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Automaton pipeline description
|
||||
@subsubsection Describing instruction pipeline characteristics
|
||||
@cindex automaton based pipeline description
|
||||
@ -6041,6 +6089,8 @@ construction
|
||||
@end smallexample
|
||||
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Comparison of the two descriptions
|
||||
@subsubsection Drawbacks of the old pipeline description
|
||||
@cindex old pipeline description
|
||||
@ -6094,6 +6144,8 @@ In an automaton based pipeline hazard recognizer, speed is not dependent
|
||||
on processor complexity.
|
||||
@end itemize
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Conditional Execution
|
||||
@section Conditional Execution
|
||||
@cindex conditional execution
|
||||
@ -6174,6 +6226,8 @@ generates a new pattern
|
||||
"(%3) add %2,%1,%0")
|
||||
@end smallexample
|
||||
|
||||
@end ifset
|
||||
@ifset INTERNALS
|
||||
@node Constant Definitions
|
||||
@section Constant Definitions
|
||||
@cindex constant definitions
|
||||
|
Loading…
Reference in New Issue
Block a user