-This is ld.info, produced by makeinfo version 4.11 from ../../../../binutils-2.19/ld/ld.texinfo.
+This is ld.info, produced by makeinfo version 4.8 from
+/home/jingyu/projects/gcc/android-toolchain/binutils-2.19/ld/ld.texinfo.
START-INFO-DIR-ENTRY
* Ld: (ld). The GNU linker.
The default format is taken from the environment variable
`GNUTARGET'. *Note Environment::. You can also define the input
- format from a script, using the command `TARGET'; see *note Format
+ format from a script, using the command `TARGET'; see *Note Format
Commands::.
`-c MRI-COMMANDFILE'
`--mri-script=MRI-COMMANDFILE'
For compatibility with linkers produced by MRI, `ld' accepts script
files written in an alternate, restricted command language,
- described in *note MRI Compatible Script Files: MRI. Introduce
+ described in *Note MRI Compatible Script Files: MRI. Introduce
MRI script files with the option `-c'; use the `-T' option to run
linker scripts written in the general-purpose `ld' scripting
language. If MRI-CMDFILE does not exist, `ld' looks for it in the
[0x0000000c] foo = (foo * 0x4)
[0x0000000c] foo = (foo + 0x8)
- See *note Expressions:: for more information about
+ See *Note Expressions:: for more information about
expressions in linker scripts.
`-n'
Tells the linker to accept input files whose architecture cannot be
recognised. The assumption is that the user knows what they are
doing and deliberately wants to link in these unknown input files.
- This was the default behaviour of the linker, before release 2.14.
- The default behaviour from release 2.14 onwards is to reject such
- input files, and so the `--accept-unknown-input-arch' option has
- been added to restore the old behaviour.
+ This was the default behaviour of the linker, before release
+ 2.14. The default behaviour from release 2.14 onwards is to
+ reject such input files, and so the `--accept-unknown-input-arch'
+ option has been added to restore the old behaviour.
`--as-needed'
`--no-as-needed'
meaningful on ELF platforms which support shared libraries.
The format of the dynamic list is the same as the version node
- without scope and node name. See *note VERSION:: for more
+ without scope and node name. See *Note VERSION:: for more
information.
`--dynamic-list-data'
the "sysroot prefix". Otherwise, the linker will try to open the
file in the current directory. If it is not found, the linker
will search through the archive library search path. See the
- description of `-L' in *note Command Line Options: Options.
+ description of `-L' in *Note Command Line Options: Options.
If you use `INPUT (-lFILE)', `ld' will transform the name to
`libFILE.a', as with the command line argument `-l'.
The `GROUP' command is like `INPUT', except that the named files
should all be archives, and they are searched repeatedly until no
new undefined references are created. See the description of `-('
- in *note Command Line Options: Options.
+ in *Note Command Line Options: Options.
`AS_NEEDED(FILE, FILE, ...)'
`AS_NEEDED(FILE FILE ...)'
The semicolon after EXPRESSION is required.
- Expressions are defined below; see *note Expressions::.
+ Expressions are defined below; see *Note Expressions::.
You may write symbol assignments as commands in their own right, or
as statements within a `SECTIONS' command, or as part of an output
section description in a `SECTIONS' command.
The section of the symbol will be set from the section of the
-expression; for more information, see *note Expression Section::.
+expression; for more information, see *Note Expression Section::.
Here is an example showing the three different places that symbol
assignments may be used:
may consist of any sequence of characters, but a name which contains
any unusual characters such as commas must be quoted.
- The output section name `/DISCARD/' is special; *note Output Section
+ The output section name `/DISCARD/' is special; *Note Output Section
Discarding::.
\1f
second will set it to the current value of the location counter aligned
to the strictest alignment of a `.text' input section.
- The ADDRESS may be an arbitrary expression; *note Expressions::.
+ The ADDRESS may be an arbitrary expression; *Note Expressions::.
For example, if you want to align the section on a 0x10 byte boundary,
so that the lowest four bits of the section address are zero, you could
do something like this:
OUTPUT-SECTION-COMMAND
...
} [>REGION] [AT>LMA_REGION] [:PHDR :PHDR ...] [=FILLEXP]
-We've already described SECTION, ADDRESS, and OUTPUT-SECTION-COMMAND.
-In this section we will describe the remaining section attributes.
+We've already described SECTION, ADDRESS, and
+OUTPUT-SECTION-COMMAND. In this section we will describe the remaining
+section attributes.
* Menu:
..........................
Every section has a virtual address (VMA) and a load address (LMA); see
-*note Basic Script Concepts::. The address expression which may appear
+*Note Basic Script Concepts::. The address expression which may appear
in an output section description sets the VMA (*note Output Section
Address::).
.text0 { o1/*.o(.text) }
.text1 { o2/*.o(.text) }
}
-This will define both `.text0' and `.text1' to start at address 0x1000.
-`.text0' will be loaded at address 0x4000, and `.text1' will be loaded
-immediately after `.text0'. The following symbols will be defined if
-referenced: `__load_start_text0', `__load_stop_text0',
+This will define both `.text0' and `.text1' to start at address
+0x1000. `.text0' will be loaded at address 0x4000, and `.text1' will
+be loaded immediately after `.text0'. The following symbols will be
+defined if referenced: `__load_start_text0', `__load_stop_text0',
`__load_start_text1', `__load_stop_text1'.
C code to copy overlay `.text1' into the overlay area might look
around to fit into the available regions.
A linker script may contain at most one use of the `MEMORY' command.
-However, you can define as many blocks of memory within it as you wish.
-The syntax is:
+However, you can define as many blocks of memory within it as you
+wish. The syntax is:
MEMORY
{
NAME [(ATTR)] : ORIGIN = ORIGIN, LENGTH = LEN
The ATTR string is an optional list of attributes that specify
whether to use a particular memory region for an input section which is
-not explicitly mapped in the linker script. As described in *note
+not explicitly mapped in the linker script. As described in *Note
SECTIONS::, if you do not specify an output section for some input
section, the linker will create an output section with the same name as
the input section. If you define region attributes, the linker will use
variable = ALIGN(0x8000);
}
... }
- The first use of `ALIGN' in this example specifies the location of
- a section because it is used as the optional ADDRESS attribute of
- a section definition (*note Output Section Address::). The second
- use of `ALIGN' is used to defines the value of a symbol.
+ The first use of `ALIGN' in this example specifies the
+ location of a section because it is used as the optional ADDRESS
+ attribute of a section definition (*note Output Section
+ Address::). The second use of `ALIGN' is used to defines the
+ value of a symbol.
The builtin function `NEXT' is closely related to `ALIGN'.
target subroutine is a leaf routine (that is, the target subroutine does
not itself call any subroutines).
+ The `--fix-cortex-a8' switch enables a link-time workaround for an
+erratum in certain Cortex-A8 processors. The workaround is enabled by
+default if you are targeting the ARM v7-A architecture profile. It can
+be enabled otherwise by specifying `--fix-cortex-a8', or disabled
+unconditionally by specifying `--no-fix-cortex-a8'.
+
+ The erratum only affects Thumb-2 code. Please contact ARM for
+further details.
+
\1f
File: ld.info, Node: M68HC11/68HC12, Next: PowerPC ELF32, Prev: MSP430, Up: Machine Dependent
The value of `N', the parameter to the `--stub-group-size=' option
controls where the stub groups are placed. If it is negative then all
-stubs are placed before the first branch that needs them. If it is
+stubs are placed after the first branch that needs them. If it is
positive then the stubs can be placed either before or after the
branches that need them. If the value of `N' is 1 (either +1 or -1)
then the linker will choose exactly where to place groups of stubs,
==================================
This section describes some of the win32 specific `ld' issues. See
-*note Command Line Options: Options. for detailed description of the
+*Note Command Line Options: Options. for detailed description of the
command line options mentioned here.
_import libraries_
Often people omit facts because they think they know what causes the
problem and assume that some details do not matter. Thus, you might
assume that the name of a symbol you use in an example does not matter.
-Well, probably it does not, but one cannot be sure. Perhaps the bug is
-a stray memory reference which happens to fetch from the location where
-that name is stored in memory; perhaps, if the name were different, the
-contents of that location would fool the linker into doing the right
-thing despite the bug. Play it safe and give a specific, complete
-example. That is the easiest thing for you to do, and the most helpful.
+Well, probably it does not, but one cannot be sure. Perhaps the bug
+is a stray memory reference which happens to fetch from the location
+where that name is stored in memory; perhaps, if the name were
+different, the contents of that location would fool the linker into
+doing the right thing despite the bug. Play it safe and give a
+specific, complete example. That is the easiest thing for you to do,
+and the most helpful.
Keep in mind that the purpose of a bug report is to enable us to fix
the bug if it is new to us. Therefore, always write your bug reports
To aid users making the transition to GNU `ld' from the MRI linker,
`ld' can use MRI compatible linker scripts as an alternative to the
-more general-purpose linker scripting language described in *note
+more general-purpose linker scripting language described in *Note
Scripts::. MRI compatible linker scripts have a much simpler command
set than the scripting language otherwise used with `ld'. GNU `ld'
supports the most commonly used MRI linker commands; these commands are
H. Include an unaltered copy of this License.
I. Preserve the section entitled "History", and its title, and add
to it an item stating at least the title, year, new authors, and
- publisher of the Modified Version as given on the Title Page. If
- there is no section entitled "History" in the Document, create
- one stating the title, year, authors, and publisher of the
- Document as given on its Title Page, then add an item
+ publisher of the Modified Version as given on the Title Page.
+ If there is no section entitled "History" in the Document,
+ create one stating the title, year, authors, and publisher of
+ the Document as given on its Title Page, then add an item
describing the Modified Version as stated in the previous
sentence.
J. Preserve the network location, if any, given in the Document for
- public access to a Transparent copy of the Document, and likewise
- the network locations given in the Document for previous versions
- it was based on. These may be placed in the "History" section.
- You may omit a network location for a work that was published at
- least four years before the Document itself, or if the original
- publisher of the version it refers to gives permission.
+ public access to a Transparent copy of the Document, and
+ likewise the network locations given in the Document for
+ previous versions it was based on. These may be placed in the
+ "History" section. You may omit a network location for a work
+ that was published at least four years before the Document
+ itself, or if the original publisher of the version it refers
+ to gives permission.
K. In any section entitled "Acknowledgements" or "Dedications",
preserve the section's title, and preserve in the section all the
substance and tone of each of the contributor acknowledgements
* --fatal-warnings: Options. (line 837)
* --file-alignment: Options. (line 1533)
* --filter: Options. (line 228)
+* --fix-cortex-a8: i960. (line 39)
* --fix-v4bx: ARM. (line 44)
* --fix-v4bx-interworking: ARM. (line 57)
* --force-dynamic: Options. (line 434)
* --no-dotsyms: PowerPC64 ELF64. (line 33)
* --no-enum-size-warning: ARM. (line 106)
* --no-fatal-warnings: Options. (line 837)
+* --no-fix-cortex-a8: i960. (line 39)
* --no-gc-sections: Options. (line 852)
* --no-keep-memory: Options. (line 895)
* --no-multi-toc: PowerPC64 ELF64. (line 74)
* ALIGN(EXP,ALIGN): Builtin Functions. (line 36)
* ALIGN(SECTION_ALIGN): Forced Output Alignment.
(line 6)
-* ALIGNOF(SECTION): Builtin Functions. (line 61)
+* ALIGNOF(SECTION): Builtin Functions. (line 62)
* allocating memory: MEMORY. (line 6)
* architecture: Miscellaneous Commands.
(line 72)
* BFD requirements: BFD. (line 16)
* big-endian objects: Options. (line 200)
* binary input format: Options. (line 117)
-* BLOCK(EXP): Builtin Functions. (line 74)
+* BLOCK(EXP): Builtin Functions. (line 75)
* bug criteria: Bug Criteria. (line 6)
* bug reports: Bug Reporting. (line 6)
* bugs in ld: Reporting Bugs. (line 6)
* constructors: Options. (line 511)
* constructors, arranging in link: Output Section Keywords.
(line 19)
+* Cortex-A8 erratum workaround: i960. (line 39)
* crash of linker: Bug Criteria. (line 9)
* CREATE_OBJECT_SYMBOLS: Output Section Keywords.
(line 9)
* data: Output Section Data.
(line 6)
* DATA_SEGMENT_ALIGN(MAXPAGESIZE, COMMONPAGESIZE): Builtin Functions.
- (line 79)
-* DATA_SEGMENT_END(EXP): Builtin Functions. (line 100)
-* DATA_SEGMENT_RELRO_END(OFFSET, EXP): Builtin Functions. (line 106)
+ (line 80)
+* DATA_SEGMENT_END(EXP): Builtin Functions. (line 101)
+* DATA_SEGMENT_RELRO_END(OFFSET, EXP): Builtin Functions. (line 107)
* dbx: Options. (line 1174)
* DEF files, creating: Options. (line 1597)
* default emulation: Environment. (line 21)
* default input format: Environment. (line 9)
-* DEFINED(SYMBOL): Builtin Functions. (line 117)
+* DEFINED(SYMBOL): Builtin Functions. (line 118)
* deleting local symbols: Options. (line 536)
* demangling, default: Environment. (line 29)
* demangling, from command line: Options. (line 818)
* grouping input files: File Commands. (line 47)
* groups of archives: Options. (line 645)
* H8/300 support: H8/300. (line 6)
-* header size: Builtin Functions. (line 182)
+* header size: Builtin Functions. (line 183)
* heap size: Options. (line 1539)
* help: Options. (line 883)
* holes: Location Counter. (line 12)
* LDEMULATION: Environment. (line 21)
* len =: MEMORY. (line 72)
* LENGTH =: MEMORY. (line 72)
-* LENGTH(MEMORY): Builtin Functions. (line 134)
+* LENGTH(MEMORY): Builtin Functions. (line 135)
* library search path in linker script: File Commands. (line 74)
* link map: Options. (line 352)
* link-time runtime library search path: Options. (line 1063)
* little-endian objects: Options. (line 203)
* LOAD (MRI): MRI. (line 84)
* load address: Output Section LMA. (line 6)
-* LOADADDR(SECTION): Builtin Functions. (line 137)
+* LOADADDR(SECTION): Builtin Functions. (line 138)
* loading, preventing: Output Section Type.
(line 22)
* local symbols, deleting: Options. (line 540)
(line 72)
* machine dependencies: Machine Dependent. (line 6)
* mapping input sections to output sections: Input Section. (line 6)
-* MAX: Builtin Functions. (line 142)
+* MAX: Builtin Functions. (line 143)
* MEMORY: MEMORY. (line 6)
* memory region attributes: MEMORY. (line 32)
* memory regions: MEMORY. (line 6)
* memory regions and sections: Output Section Region.
(line 6)
* memory usage: Options. (line 895)
-* MIN: Builtin Functions. (line 145)
+* MIN: Builtin Functions. (line 146)
* Motorola 68K GOT generation: M68K. (line 6)
* MRI compatibility: MRI. (line 6)
* MSP430 extra sections: MSP430. (line 11)
(line 6)
* names: Symbols. (line 6)
* naming the output file: Options. (line 409)
-* NEXT(EXP): Builtin Functions. (line 149)
+* NEXT(EXP): Builtin Functions. (line 150)
* NMAGIC: Options. (line 389)
* NO_ENUM_SIZE_WARNING: ARM. (line 106)
* NO_WCHAR_SIZE_WARNING: ARM. (line 113)
(line 56)
* NOLOAD: Output Section Type.
(line 22)
-* not enough room for program headers: Builtin Functions. (line 187)
+* not enough room for program headers: Builtin Functions. (line 188)
* o =: MEMORY. (line 67)
* objdump -i: BFD. (line 6)
* object file management: BFD. (line 6)
* ORDER (MRI): MRI. (line 95)
* org =: MEMORY. (line 67)
* ORIGIN =: MEMORY. (line 67)
-* ORIGIN(MEMORY): Builtin Functions. (line 155)
+* ORIGIN(MEMORY): Builtin Functions. (line 156)
* orphan: Orphan Sections. (line 6)
* output file after errors: Options. (line 965)
* output file format in linker script: Format Commands. (line 10)
* program headers: PHDRS. (line 6)
* program headers and sections: Output Section Phdr.
(line 6)
-* program headers, not enough room: Builtin Functions. (line 187)
+* program headers, not enough room: Builtin Functions. (line 188)
* program segments: PHDRS. (line 6)
* PROVIDE: PROVIDE. (line 6)
* PROVIDE_HIDDEN: PROVIDE_HIDDEN. (line 6)
* section address: Output Section Address.
(line 6)
* section address in expression: Builtin Functions. (line 17)
-* section alignment: Builtin Functions. (line 61)
+* section alignment: Builtin Functions. (line 62)
* section alignment, warnings on: Options. (line 1329)
* section data: Output Section Data.
(line 6)
* section fill pattern: Output Section Fill.
(line 6)
* section load address: Output Section LMA. (line 6)
-* section load address in expression: Builtin Functions. (line 137)
+* section load address in expression: Builtin Functions. (line 138)
* section name: Output Section Name.
(line 6)
* section name wildcard patterns: Input Section Wildcards.
(line 6)
-* section size: Builtin Functions. (line 166)
+* section size: Builtin Functions. (line 167)
* section, assigning to memory region: Output Section Region.
(line 6)
* section, assigning to program header: Output Section Phdr.
* sections, discarding: Output Section Discarding.
(line 6)
* segment origins, cmd line: Options. (line 1190)
-* SEGMENT_START(SEGMENT, DEFAULT): Builtin Functions. (line 158)
+* SEGMENT_START(SEGMENT, DEFAULT): Builtin Functions. (line 159)
* segments, ELF: PHDRS. (line 6)
* shared libraries: Options. (line 1120)
* SHORT(EXPRESSION): Output Section Data.
(line 6)
-* SIZEOF(SECTION): Builtin Functions. (line 166)
-* SIZEOF_HEADERS: Builtin Functions. (line 182)
+* SIZEOF(SECTION): Builtin Functions. (line 167)
+* SIZEOF_HEADERS: Builtin Functions. (line 183)
* small common symbols: Input Section Common.
(line 20)
* SORT: Input Section Wildcards.
* SUBALIGN(SUBSECTION_ALIGN): Forced Input Alignment.
(line 6)
* suffixes for integers: Constants. (line 12)
-* symbol defaults: Builtin Functions. (line 117)
+* symbol defaults: Builtin Functions. (line 118)
* symbol definition, scripts: Assignments. (line 6)
* symbol names: Symbols. (line 6)
* symbol tracing: Options. (line 546)
* traditional format: Options. (line 1169)
* trampoline generation on M68HC11: M68HC11/68HC12. (line 31)
* trampoline generation on M68HC12: M68HC11/68HC12. (line 31)
-* unallocated address, next: Builtin Functions. (line 149)
+* unallocated address, next: Builtin Functions. (line 150)
* undefined symbol: Options. (line 503)
* undefined symbol in linker script: Miscellaneous Commands.
(line 13)
\1f
Tag Table:
-Node: Top\7f777
-Node: Overview\7f1548
-Node: Invocation\7f2662
-Node: Options\7f3070
-Node: Environment\7f85534
-Node: Scripts\7f87294
-Node: Basic Script Concepts\7f89028
-Node: Script Format\7f91735
-Node: Simple Example\7f92598
-Node: Simple Commands\7f95694
-Node: Entry Point\7f96145
-Node: File Commands\7f96904
-Node: Format Commands\7f100905
-Node: Miscellaneous Commands\7f102871
-Node: Assignments\7f106250
-Node: Simple Assignments\7f106741
-Node: PROVIDE\7f108477
-Node: PROVIDE_HIDDEN\7f109682
-Node: Source Code Reference\7f109926
-Node: SECTIONS\7f113506
-Node: Output Section Description\7f115397
-Node: Output Section Name\7f116450
-Node: Output Section Address\7f117326
-Node: Input Section\7f118975
-Node: Input Section Basics\7f119776
-Node: Input Section Wildcards\7f122994
-Node: Input Section Common\7f127727
-Node: Input Section Keep\7f129209
-Node: Input Section Example\7f129699
-Node: Output Section Data\7f130667
-Node: Output Section Keywords\7f133444
-Node: Output Section Discarding\7f137013
-Node: Output Section Attributes\7f138194
-Node: Output Section Type\7f139197
-Node: Output Section LMA\7f140351
-Node: Forced Output Alignment\7f142864
-Node: Forced Input Alignment\7f143132
-Node: Output Section Region\7f143517
-Node: Output Section Phdr\7f143947
-Node: Output Section Fill\7f144611
-Node: Overlay Description\7f145753
-Node: MEMORY\7f150055
-Node: PHDRS\7f154254
-Node: VERSION\7f159293
-Node: Expressions\7f167085
-Node: Constants\7f167963
-Node: Symbols\7f168524
-Node: Orphan Sections\7f169262
-Node: Location Counter\7f170426
-Node: Operators\7f174862
-Node: Evaluation\7f175784
-Node: Expression Section\7f177148
-Node: Builtin Functions\7f178637
-Node: Implicit Linker Scripts\7f186599
-Node: Machine Dependent\7f187374
-Node: H8/300\7f188390
-Node: i960\7f190015
-Node: M68HC11/68HC12\7f191700
-Node: ARM\7f193154
-Node: HPPA ELF32\7f200404
-Node: M68K\7f202027
-Node: MMIX\7f202936
-Node: MSP430\7f204101
-Node: PowerPC ELF32\7f205150
-Node: PowerPC64 ELF64\7f207764
-Node: SPU ELF\7f212180
-Node: TI COFF\7f214812
-Node: WIN32\7f215338
-Node: Xtensa\7f233695
-Node: BFD\7f236817
-Node: BFD outline\7f238272
-Node: BFD information loss\7f239558
-Node: Canonical format\7f242075
-Node: Reporting Bugs\7f246432
-Node: Bug Criteria\7f247126
-Node: Bug Reporting\7f247825
-Node: MRI\7f254864
-Node: GNU Free Documentation License\7f259507
-Node: LD Index\7f279212
+Node: Top\7f808
+Node: Overview\7f1579
+Node: Invocation\7f2693
+Node: Options\7f3101
+Node: Environment\7f85566
+Node: Scripts\7f87326
+Node: Basic Script Concepts\7f89060
+Node: Script Format\7f91767
+Node: Simple Example\7f92630
+Node: Simple Commands\7f95726
+Node: Entry Point\7f96177
+Node: File Commands\7f96936
+Node: Format Commands\7f100937
+Node: Miscellaneous Commands\7f102903
+Node: Assignments\7f106282
+Node: Simple Assignments\7f106773
+Node: PROVIDE\7f108509
+Node: PROVIDE_HIDDEN\7f109714
+Node: Source Code Reference\7f109958
+Node: SECTIONS\7f113538
+Node: Output Section Description\7f115429
+Node: Output Section Name\7f116482
+Node: Output Section Address\7f117358
+Node: Input Section\7f119007
+Node: Input Section Basics\7f119808
+Node: Input Section Wildcards\7f123026
+Node: Input Section Common\7f127759
+Node: Input Section Keep\7f129241
+Node: Input Section Example\7f129731
+Node: Output Section Data\7f130699
+Node: Output Section Keywords\7f133476
+Node: Output Section Discarding\7f137045
+Node: Output Section Attributes\7f138226
+Node: Output Section Type\7f139230
+Node: Output Section LMA\7f140384
+Node: Forced Output Alignment\7f142897
+Node: Forced Input Alignment\7f143165
+Node: Output Section Region\7f143550
+Node: Output Section Phdr\7f143980
+Node: Output Section Fill\7f144644
+Node: Overlay Description\7f145786
+Node: MEMORY\7f150089
+Node: PHDRS\7f154289
+Node: VERSION\7f159328
+Node: Expressions\7f167120
+Node: Constants\7f167998
+Node: Symbols\7f168559
+Node: Orphan Sections\7f169297
+Node: Location Counter\7f170461
+Node: Operators\7f174897
+Node: Evaluation\7f175819
+Node: Expression Section\7f177183
+Node: Builtin Functions\7f178672
+Node: Implicit Linker Scripts\7f186639
+Node: Machine Dependent\7f187414
+Node: H8/300\7f188430
+Node: i960\7f190055
+Node: M68HC11/68HC12\7f192156
+Node: ARM\7f193610
+Node: HPPA ELF32\7f200859
+Node: M68K\7f202482
+Node: MMIX\7f203391
+Node: MSP430\7f204556
+Node: PowerPC ELF32\7f205605
+Node: PowerPC64 ELF64\7f208219
+Node: SPU ELF\7f212635
+Node: TI COFF\7f215267
+Node: WIN32\7f215793
+Node: Xtensa\7f234150
+Node: BFD\7f237272
+Node: BFD outline\7f238727
+Node: BFD information loss\7f240013
+Node: Canonical format\7f242530
+Node: Reporting Bugs\7f246887
+Node: Bug Criteria\7f247581
+Node: Bug Reporting\7f248280
+Node: MRI\7f255319
+Node: GNU Free Documentation License\7f259962
+Node: LD Index\7f279679
\1f
End Tag Table