Lines Matching full:symbols

40   Export all symbols (normally combined with --no-gc-sections)
48   When building an executable, export any non-hidden symbols.  By default only
49   the entry point and any symbols marked as exports (either via the command line
74   Allow undefined symbols in linked binary.  This is the legacy
75   flag which corresponds to ``--unresolve-symbols=ignore`` +
81   symbols, one per line, which are allowed to be undefined.
83 .. option:: --unresolved-symbols=<method>
90      Report all unresolved symbols.  This is the default.  Normally the linker
92      option ``--warn-unresolved-symbols`` can change this to a warning.
96      Resolve all undefined symbols to zero.  For data and function addresses
102      Undefined symbols generate WebAssembly imports, including undefined data
103      symbols.  This is somewhat similar to the --import-undefined option but
105      relocations that are allowed for imported data symbols.  Relocations that
111      symbols are resolved by a dynamic linker.  Since the dynamic linking API is
121    Generate WebAssembly imports for undefined symbols, where possible.  For
122    example, for function symbols this is always possible, but in general this
123    is not possible for undefined data symbols.  Undefined data symbols will
124    still be reported as normal (in accordance with ``--unresolved-symbols``).
176 When building a shared library any symbols marked as ``visibility=default`` will
179 When building an executable, only the entry point (``_start``) and symbols with
184 In addition, symbols can be exported via the linker command line using
189 used to export symbols in the executable which are marked as
195 By default no undefined symbols are allowed in the final binary.  The flag
197 undefined symbol.  It is then up to the runtime to provide such symbols.
198 ``--allow-undefined-file`` is the same but allows a list of symbols to be
201 Alternatively symbols can be marked in the source code as with the
212 library is a stand-in for a set of symbols that will be available at runtime,
214 symbols, one per line.  Each symbol can specify zero or more dependencies.
215 These dependencies are symbols that must be defined, and exported, by the output
238 The symbols which are preserved by default are: