Port nextpnr-{ice40,ecp5} to WASI #447
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This involves very few changes, all typical to WASM ports:
* WASM doesn't currently support threads or atomics so those are
disabled.
* WASM doesn't currently support exceptions so the exception
machinery is stubbed out.
* WASM doesn't (and can't) have mmap(), so an emulation library is
used. That library currently doesn't support MAP_SHARED flags,
so MAP_PRIVATE is used instead.
There is also an update to bring ECP5 bbasm CMake rules to parity
with iCE40 ones, since although it is possible to embed chipdb into
nextpnr on WASM, a 200 MB WASM file has very few practical uses.
The README is not updated and there is no included toolchain file
because at the moment it's not possible to build nextpnr with
upstream boost and wasi-libc. Boost requires a patch (merged, will
be available in boost 1.74.0), wasi-libc requires a few unmerged
patches.
|
@whitequark @daveshah1 LGTM as well, default behavior seams unaffected. |
|
Updated instructions as of 2020-06-22:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This involves very few changes, all typical to WASM ports:
MAP_SHAREDflags, soMAP_PRIVATEis used instead.There is also an update to bring ECP5 bbasm CMake rules to parity with iCE40 ones, since although it is possible to embed chipdb into nextpnr on WASM, a 200 MB WASM file has very few practical uses.
The README is not updated and there is no included toolchain file because at the moment it's not possible to build nextpnr with upstream boost and wasi-libc. Boost requires a patch (merged, will be available in boost 1.74.0), wasi-libc requires a few unmerged patches.
Nevertheless I will briefly describe in this PR how to build it.
$WASI_SDKto the location where it's unpackedsysroot/lib/wasm32-wasi/libwasi-emulated-mman.a-lwasi-emulated-mmaninCMakeLists.txtwith the full path tolibwasi-emulated-mman.aproject-config.jam(replacing<WASI-SDK>as appropriate) and run./b2 threading=single link=static-DUSE_C_EMBED=ON. This will fail because your compiler probably doesn't support#embedbut that's okToolchain-WASI.cmakecmake .. -DCMAKE_TOOLCHAIN_FILE=Toolchain-WASI.cmake -DSTATIC_BUILD=ON -DBOOST_ROOT=<Boost root> -DIMPORT_EXECUTABLES=<host build directory>/ImportExecutables.cmake -DARCH=<arch> -DBUILD_GUI=OFF -DBUILD_PYTHON=OFF -DEXTERNAL_CHIPDB=ON -DEXTERNAL_CHIPDB_ROOT=/share/nextpnrmake. You should have anextpnr-<arch>.wasmnowwasmtime run ./nextpnr-<arch>.wasm --dir . --mapdir /share/nextpnr/<arch>::<host build directory>/<arch>/chipdbs -- <args>where<args>are the normal nextpnr arguments