Lines Matching full:emulation
85 * Emulation Walkthrough:: A Walkthrough of a Typical Emulation
99 Each linker target has an @dfn{emulation}. The emulation includes the
120 script will create the emulation source file, which contains C code.
121 This C code permits the linker emulation to override various linker
122 behaviours. Most targets use the generic emulation code, which is in
126 emulation parameters script in the @file{emulparams} directory, a linker
128 emulation source file generation script in the @file{emultempl}
133 @file{scripttempl/aout.sc}, and creates the emulation code using
137 depending upon how it is configured. An emulation can be selected with
142 * emulation parameters:: @file{emulparams} scripts
147 @node emulation parameters
153 building an emulation source file.
156 is set to @var{emul} in @file{configure.tgt}. The name of the emulation
238 selection is controlled by the @code{get_script} emulation entry point;
242 in the linker command language, to standard output. If the emulation
406 emulation code. The name of the @file{emultempl} script is set by the
426 the name of the emulation set in @file{configure.tgt} (this is also the
434 as well as strings for the emulation name (normally set from the shell
441 default emulation. In this case, the @file{emultempl} script should
443 @code{get_scripts} entry point. When the emulation is not the default,
447 At some point, the linker emulation entry points should be documented.
449 @node Emulation Walkthrough
450 @chapter A Walkthrough of a Typical Emulation
456 the emulation will be called. It will, hopefully, give you enough
461 @code{main} is defined. The bulk of the code that's emulation
462 specific will initially be in @code{emultempl/@var{emulation}.em} but
463 will end up in @code{e@var{emulation}.c} when the build is done.
466 defines the @code{ld_emulation_xfer_struct} structure your emulation
469 Your emulation file exports a symbol
470 @code{ld_@var{EMULATION_NAME}_emulation}. If your emulation is
474 to your emulation, like @code{ldemul_after_parse} which simply calls
475 your @code{ld_@var{EMULATION}_emulation.after_parse} function. For
477 should assume the indirect reference to your emulation also.
482 After initialization, @code{main} selects an emulation by pre-scanning
491 If the emulation doesn't recognize it, then parse_args checks to see
494 Now that the emulation has had access to all its command-line options,
497 to set up any variables needed by the emulation script.
499 @code{main} now calls @code{ldemul_get_script} to get the emulation
506 the emulation wants to handle some files specially. All the while,
514 appears to be the main core of the linking itself, as far as emulation
525 details. Your emulation is usually concerned more with managing
558 @item @file{emultempl/@var{EMULATION}.em} has your code
