PR to 9fc93a4

.cargo/config

@@ -1,2 +1,2 @@
 [build]
-rustflags = ["-C", "link-args=-Wl,--export-dynamic"]
+rustflags = ["-C", "link-args=-rdynamic"]

.dockerignore

@@ -1 +1 @@
-target
+*

.editorconfig

@@ -0,0 +1,12 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_size = 4
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[Makefile]
+indent_style = tab

.gitattributes

@@ -0,0 +1,8 @@
+# Auto detect text and normalize to LF on commit regardless of "core.autocrlf".
+# See: https://help.github.com/en/articles/dealing-with-line-endings#example
+* text=auto eol=lf
+
+# Denote all files that are truly binary and should not be modified.
+*.png binary
+*.jpg binary
+*.wasm binary

.github/actions/test/action.yml

@@ -0,0 +1,18 @@
+name: 'Test Lucet'
+description: 'run tests using standardized lucet development environment'
+inputs:
+  target:
+    description: "Makefile target to execute"
+    required: true
+runs:
+  using: 'docker'
+  image: '../../../Dockerfile'
+  # The Dockerfile does not specify an entrypoint.
+  entrypoint: "/bin/sh"
+  args:
+      # Next arg is a command for sh to execute.
+    - '-c'
+      # rustup expects $HOME to be set to /root during `docker run` because thats what
+      # it was set to during container creation. Actions clears $HOME so we set it here.
+      # The test target of the Makefile is our standard CI.
+    - 'export HOME=/root; make ${{ inputs.target }}'

.github/workflows/fuzz.yml

@@ -0,0 +1,50 @@
+name: Fuzz
+on:
+  schedule:
+    - cron: "0 0 * * *"
+
+jobs:
+  fuzz:
+    name: Fuzz lucet-wasi
+
+    runs-on: ubuntu-16.04
+    steps:
+    - uses: actions/checkout@v1
+      with:
+        submodules: true
+
+    - name: Install Rust (rustup)
+      run: rustup update
+
+    - name: Install wasi-sdk (ubuntu)
+      run: |
+        curl -sS -L -O https://github.com/CraneStation/wasi-sdk/releases/download/wasi-sdk-7/wasi-sdk_7.0_amd64.deb
+        sudo dpkg -i wasi-sdk_7.0_amd64.deb
+
+    - name: Install native clang, csmith tools
+      run: |
+        sudo apt-get install -y --no-install-recommends \
+          software-properties-common \
+          clang-6.0 \
+          gcc-multilib \
+          csmith \
+          libcsmith-dev \
+          creduce
+        sudo update-alternatives --install /usr/bin/clang clang /usr/bin/clang-6.0 100
+
+    - name: Build Binaryen tools
+      run: |
+        curl -sS -L "https://github.com/WebAssembly/binaryen/archive/version_${BINARYEN_VERSION}.tar.gz" | tar xzf -
+        mkdir -p binaryen-build
+        cd binaryen-build && cmake "../binaryen-version_${BINARYEN_VERSION}" && make wasm-opt wasm-reduce
+        echo "##[add-path]$PWD/binaryen-build/bin"
+      env:
+        BINARYEN_VERSION: 86
+
+    - name: Test lucet-wasi-fuzz with known seed
+      run: make test-fuzz
+
+    - name: Fuzz
+      env:
+          FUZZ_NUM_TESTS: 100000
+      run: make fuzz

.github/workflows/mac-ci.yml.disabled

@@ -0,0 +1,29 @@
+name: Mac OS CI
+on: [push, pull_request]
+
+jobs:
+  test:
+    name: Test
+    runs-on: macos-latest
+    steps:
+    - uses: actions/checkout@master
+      with:
+        submodules: true
+
+    - name: Install Rust (macos)
+      run: |
+        curl https://sh.rustup.rs | sh -s -- -y
+        rustup update
+        echo "##[add-path]$HOME/.cargo/bin"
+
+    - name: Install wasi-sdk (macos)
+      run: |
+        curl -sS -L -O https://github.com/CraneStation/wasi-sdk/releases/download/wasi-sdk-7/wasi-sdk-7.0-macos.tar.gz
+        tar xf wasi-sdk-7.0-macos.tar.gz
+        sudo mv wasi-sdk-7.0/opt /opt
+
+    - name: Test Lucet
+      run: make test-except-fuzz
+
+    - name: Ensure testing did not change sources
+      run: git diff --exit-code

.github/workflows/main.yml

@@ -0,0 +1,51 @@
+name: CI
+on: [push, pull_request]
+
+jobs:
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v1
+      with:
+        submodules: true
+
+    # Testing uses the development environment Docker container.
+    # This action builds the container and executes the test suite inside it.
+    - uses: ./.github/actions/test
+      with:
+        target: test-full
+
+    - name: Ensure testing did not change sources
+      run: git diff --exit-code
+
+  package:
+    name: Package
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v1
+      with:
+        submodules: true
+
+    # Testing uses the development environment Docker container.
+    # This action builds the container and executes the test suite inside it.
+    - uses: ./.github/actions/test
+      with:
+        target: package
+
+    - name: Ensure testing did not change sources
+      run: git diff --exit-code
+
+
+  rustfmt:
+    name: Rustfmt
+    runs-on: ubuntu-16.04
+    steps:
+    - uses: actions/checkout@v1
+      with:
+        submodules: true
+    - name: Install Rust (rustup)
+      run: |
+        rustup update
+        rustup component add rustfmt
+    - run: make indent-check

.gitignore

@@ -1,4 +1,8 @@
 target/
 *.rs.bk
 *.pyc
-host
+
+# devenv-installed directory
+/host
+
+core.*

.gitmodules

@@ -1,15 +1,12 @@
 [submodule "cranelift"]
 	path = cranelift
 	url = https://github.com/cranestation/cranelift
-[submodule "faerie"]
-	path = faerie
-	url = https://github.com/m4b/faerie
 [submodule "lucet-spectest/spec"]
 	path = lucet-spectest/spec
 	url = https://github.com/webassembly/spec
-[submodule "pwasm-validation"]
-	path = pwasm-validation
-	url = https://github.com/pchickey/pwasm-validator
 [submodule "sightglass"]
 	path = sightglass
 	url = https://github.com/fastly/sightglass
+[submodule "wasi"]
+	path = wasi
+	url = https://github.com/webassembly/wasi

.rustfmt.toml

@@ -0,0 +1 @@
+# This file tells tools we use rustfmt. We use the default settings.

CODE_OF_CONDUCT.md

@@ -1,18 +1,14 @@
 # Contributor Covenant Code of Conduct
 
+*Note*: this Code of Conduct pertains to individuals' behavior. Please also see the [Organizational Code of Conduct][OCoC].
+
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to creating a positive environment include:
 
 * Using welcoming and inclusive language
 * Being respectful of differing viewpoints and experiences
@@ -22,56 +18,32 @@ include:
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
 * Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [email protected], or [email protected]
-if the message is sensitive. All complaints will be reviewed and investigated
-and will result in a response that is deemed necessary and appropriate to the
-circumstances. The project team is obligated to maintain confidentiality with
-regard to the reporter of an incident.  Further details of specific enforcement
-policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Bytecode Alliance CoC team at [[email protected]](mailto:[email protected]). The CoC team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The CoC team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the Bytecode Alliance's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
+[OCoC]: ORG_CODE_OF_CONDUCT.md
 [homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+[version]: https://www.contributor-covenant.org/version/1/4/