Lines Matching defs:symbols

113 // to non-lazily-loaded dylib symbols. The main difference is that the
183 // Stores bind opcodes for telling dyld which symbols to load non-lazily.
202 // Stores bind opcodes for telling dyld which weak symbols need coalescing.
205 // 1) Non-weak definitions: This is a symbol definition that weak symbols in
211 // symbols by name, but do not specify which dylib to load them from.
250 // We will first describe how non-weak symbols are handled.
266 // With weak symbols, the situation is slightly different. Since there is no
267 // "weak lazy" lookup, function calls to weak symbols are always non-lazily
276 // address of the target symbols on load. LazyPointerSection and
319 // program. Apple Clang produces undefined symbols to each stub, such as
329 bool isNeeded() const override { return !symbols.empty(); }
337 std::vector<Defined *> symbols;
343 // particular, this happens when branch relocations target weak symbols.
375 // Stores a trie that describes the set of exported symbols.
455 // all local symbols first, then external symbols, and finally undefined
456 // symbols. For each symbol type, the LC_DYSYMTAB load command will record the
457 // range (start index and total number) of those symbols in the symbol table.
479 // STABS symbols are always local symbols, but we represent them with special
686 // most of the metadata necessary for binding symbols and rebasing addresses is
708 // - Binding entries are mostly used for symbols imported from other dylibs,
709 // but for weakly bound and interposable symbols as well. They are looked up