maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/docs/WebAssembly.rst

39 lines
1.5 KiB
ReStructuredText
Raw Normal View History

[WebAssembly] Initial wasm linker implementation This linker backend is still a work in progress but is enough to link simple programs including linking against library archives. Differential Revision: https://reviews.llvm.org/D34851 llvm-svn: 318539
2017-11-18 02:14:09 +08:00
WebAssembly lld port
====================
Revert "[WebAssembly] Update docs" This change reverts rL343155. It broke the builtbot, even though it works for me locally: http://lab.llvm.org:8011/builders/lld-sphinx-docs/builds/26336 Must be a sphinx version issue I guess. llvm-svn: 343156
2018-09-27 08:42:49 +08:00
Note: The WebAssembly port is still a work in progress and is be lacking
certain features.
[WebAssembly] Initial wasm linker implementation This linker backend is still a work in progress but is enough to link simple programs including linking against library archives. Differential Revision: https://reviews.llvm.org/D34851 llvm-svn: 318539
2017-11-18 02:14:09 +08:00
The WebAssembly version of lld takes WebAssembly binaries as inputs and produces
Revert "[WebAssembly] Update docs" This change reverts rL343155. It broke the builtbot, even though it works for me locally: http://lab.llvm.org:8011/builders/lld-sphinx-docs/builds/26336 Must be a sphinx version issue I guess. llvm-svn: 343156
2018-09-27 08:42:49 +08:00
a WebAssembly binary as its output. For the most part this port tried to mimic
the behaviour of traditional ELF linkers and specifically the ELF lld port.
Where possible that command line flags and the semantics should be the same.
[WebAssembly] Initial wasm linker implementation This linker backend is still a work in progress but is enough to link simple programs including linking against library archives. Differential Revision: https://reviews.llvm.org/D34851 llvm-svn: 318539
2017-11-18 02:14:09 +08:00
Object file format
------------------
The format the input object files that lld expects is specified as part of the
the WebAssembly tool conventions
https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md.
This is object format that the llvm will produce when run with the
[WebAssembly] Remove final -wasm component of target triple. NFC. This has been the default for a while now. llvm-svn: 332009
2018-05-11 01:59:41 +08:00
``wasm32-unknown-unknown`` target. To build llvm with WebAssembly support
[WebAssembly] Initial wasm linker implementation This linker backend is still a work in progress but is enough to link simple programs including linking against library archives. Differential Revision: https://reviews.llvm.org/D34851 llvm-svn: 318539
2017-11-18 02:14:09 +08:00
currently requires enabling the experimental backed using
``-DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly``.
Missing features
----------------
Revert "[WebAssembly] Update docs" This change reverts rL343155. It broke the builtbot, even though it works for me locally: http://lab.llvm.org:8011/builders/lld-sphinx-docs/builds/26336 Must be a sphinx version issue I guess. llvm-svn: 343156
2018-09-27 08:42:49 +08:00
There are several key features that are not yet implement in the WebAssembly
ports:
[WebAssembly] Initial support for shared objects (-shared) Based on the initial spec proposal: https://github.com/WebAssembly/tool-conventions/blob/master/DynamicLinking.md The llvm/codegen side of this is still missing but I believe this change is still worth landing as an incremental step Differential Revision: https://reviews.llvm.org/D54249 llvm-svn: 346918
2018-11-15 08:37:21 +08:00
- Support for building shared libraries via ``-shared`` is still as work in
progress.
Revert "[WebAssembly] Update docs" This change reverts rL343155. It broke the builtbot, even though it works for me locally: http://lab.llvm.org:8011/builders/lld-sphinx-docs/builds/26336 Must be a sphinx version issue I guess. llvm-svn: 343156
2018-09-27 08:42:49 +08:00
- COMDAT support. This means that support for C++ is still very limited.
- Function stripping. Currently there is no support for ``--gc-sections`` so
functions and data from a given object will linked as a unit.
- Section start/end symbols. The synthetic symbols that mark the start and
of data regions are not yet created in the output file.