Lines Matching defs:script

9 // This file contains the parser/evaluator of the linker script.
209 // should be defined from linker script.
214   return !cmd->provide || ctx.script->shouldAddProvideSym(cmd->name);
218 // linker-script-defined symbols.
280 // Collect section/value pairs of linker-script-defined symbols. This is used to
356 // Symbols defined in script should not be inlined by LTO. At the same time
554         // which are common because they are in the default bfd script.
754   // Process OVERWRITE_SECTIONS first so that it can overwrite the main script
855   // current state through to a lambda function created by the script parser.
883   OutputDesc *osd = ctx.script->createOutputSection(outsecName, "<internal>");
901   // Imagine .zed : { *(.foo) *(.bar) } script. Both foo and bar may have
948   // Last but not least, when using linker script the merge rules are forced by
949   // the script. Unfortunately, linker scripts are name based. This means that
1312     // To match the bfd linker script behaviour, only propagate program
1323   // corresponding output section. The issue is what to do with linker script
1377     // An example of such a linker script is:
1402   // given run some of the output sections in the script will be empty.
1430   // Below is an example of such linker script:
1496 LinkerScript::AddressState::AddressState(const LinkerScript &script) {
1497   for (auto &mri : script.memoryRegions) {
1503 // Here we assign addresses as instructed by linker script SECTIONS
1511     // With a linker script, assignment of addresses to headers is covered by
1555 // estimated, since general linker script arithmetic may occur afterwards.
1655 // Creates program headers as instructed by PHDRS linker script command.
1679     // Assign headers specified by linker script
1739 // zero based number of ELF header listed within PHDRS {} script block.