diff options
| -rw-r--r-- | llvm/lib/Target/WebAssembly/README.txt | 9 | ||||
| -rw-r--r-- | llvm/lib/Target/WebAssembly/known_gcc_test_failures.txt | 2 |
2 files changed, 11 insertions, 0 deletions
diff --git a/llvm/lib/Target/WebAssembly/README.txt b/llvm/lib/Target/WebAssembly/README.txt index bfb124d504e..78b3123cde8 100644 --- a/llvm/lib/Target/WebAssembly/README.txt +++ b/llvm/lib/Target/WebAssembly/README.txt @@ -12,6 +12,15 @@ binary encoding of WebAssembly itself: * https://github.com/WebAssembly/design/blob/master/AstSemantics.md * https://github.com/WebAssembly/design/blob/master/BinaryEncoding.md +The backend is built, tested and archived on the following waterfall: + https://build.chromium.org/p/client.wasm.llvm/console + +The backend's bringup is done using the GCC torture test suite first since it +doesn't require C library support. Current known failures are in +known_gcc_test_failures.txt, all other tests should pass. The waterfall will +turn red if not. Once most of these pass, further testing will use LLVM's own +test suite. + Interesting work that remains to be done: * Write a pass to restructurize irreducible control flow. This needs to be done before register allocation to be efficient, because it may duplicate basic diff --git a/llvm/lib/Target/WebAssembly/known_gcc_test_failures.txt b/llvm/lib/Target/WebAssembly/known_gcc_test_failures.txt new file mode 100644 index 00000000000..6038b198abe --- /dev/null +++ b/llvm/lib/Target/WebAssembly/known_gcc_test_failures.txt @@ -0,0 +1,2 @@ +# Tests which are known to fail from the GCC torture test suite. +# FIXME: placeholder. The script which runs the tests needs a file here! |
