Lines Matching full:undefined

72 .. option:: --allow-undefined
74   Allow undefined symbols in linked binary.  This is the legacy
76   ``--import-undefined``.
78 .. option:: --allow-undefined-file=<filename>
80   Like ``--allow-undefined``, but the filename specified a flat list of
81   symbols, one per line, which are allowed to be undefined.
85   This is a more full featured version of ``--allow-undefined``.
96      Resolve all undefined symbols to zero.  For data and function addresses
98      trapping stub function in place of the undefined function.
102      Undefined symbols generate WebAssembly imports, including undefined data
103      symbols.  This is somewhat similar to the --import-undefined option but
110      binaries that are themselves static (non-relocatable) but whose undefined
119 .. option:: --import-undefined
121    Generate WebAssembly imports for undefined symbols, where possible.  For
123    is not possible for undefined data symbols.  Undefined data symbols will
159 the target signature.  Even though this is undefined behaviour in C/C++, it is not
195 By default no undefined symbols are allowed in the final binary.  The flag
196 ``--allow-undefined`` results in a WebAssembly import being defined for each
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
203 they are expected to be undefined at static link time.
224 Here we are saying that ``foo`` is allowed to be imported (undefined) but that
226 ``free`` to the runtime.  If ``foo`` is imported (undefined), but the output
244 Weak Undefined Functions
247 On native platforms, calls to weak undefined functions end up as calls to the
251 and use this for any direct references to an undefined weak function.
253 For example a runtime call to a weak undefined function ``foo`` will up trapping
255 ``undefined:foo``.