Searched refs:WASM (Results 1 – 25 of 84) sorted by relevance
1234
/third_party/node/deps/v8/src/codegen/ |
D | code-reference.h | 25 : kind_(Kind::WASM), wasm_code_(wasm_code) {} in CodeReference() 43 bool is_wasm_code() const { return kind_ == Kind::WASM; } in is_wasm_code() 51 DCHECK_EQ(Kind::WASM, kind_); in as_wasm_code() 56 enum class Kind { NONE, JS, WASM, CODE_DESC } kind_; enumerator
|
D | code-reference.cc | 91 case Kind::WASM: \
|
/third_party/skia/modules/pathkit/ |
D | README.md | 1 PathKit WASM API 14 Run `./compile.sh` to compile a production, WASM build to `$SKIA_HOME/out/pathkit`. 21 # Build all 3 versions (release, test, debug) for both asmjs and WASM
|
/third_party/skia/modules/pathkit/npm-wasm/ |
D | README.md | 1 A WASM version of Skia's PathOps toolkit. 12 PathKit comes in two parts, a JS loader and the actual WASM code. The JS loader creates 13 a global `PathKitInit` that can be called to load the WASM code. The `locateFile` function 26 WebPack's support for WASM is still somewhat experimental, but PathKit can be
|
/third_party/node/test/fixtures/es-modules/ |
D | wasm-dep.mjs | 4 state = 'WASM JS Function Executed'; 12 state = 'WASM Start Executed';
|
/third_party/skia/third_party/externals/libwebp/ |
D | README.webp_js | 44 Web-Assembly (WASM) version: 47 CMakeLists.txt is configured to build the WASM version when using 50 See webp_js/index_wasm.html for a simple demo page using the WASM version 54 latest-upstream is recommended) and of your WASM-enabled browser to run this
|
/third_party/node/test/es-module/ |
D | test-esm-wasm.mjs | 8 describe('ESM: WASM modules', { concurrency: true }, () => { 19 'strictEqual(state, "WASM Start Executed");', 22 'strictEqual(state, "WASM JS Function Executed");',
|
/third_party/skia/site/docs/dev/design/ |
D | uni_characterize.md | 19 …include **at least** enough to allow them to function without increasing their (WASM) download size 24 …f the API is efficiency, esp. when called by **WASM** clients. There is a real cost for each JS <-…
|
/third_party/skia/modules/pathkit/npm-asmjs/ |
D | README.md | 12 PathKit comes in two parts, a JS loader and the actual WASM code. The JS loader creates 13 a global `PathKitInit` that can be called to load the WASM code. The `locateFile` function
|
/third_party/skia/modules/canvaskit/wasm_tools/SIMD/ |
D | build_simd_test.sh | 21 em++ $1 -I ../../../../ -msimd128 -Os -s WASM=1 -o output/simd_test.html
|
/third_party/skia/infra/wasm-common/ |
D | README.md | 2 build/test/perf WASM code.
|
/third_party/skia/third_party/externals/swiftshader/third_party/subzero/ |
D | .gitignore | 15 # Ignore WASM torture tests
|
D | README-wasm.md | 7 -f Makefile.standalone WASM=1 && \
|
/third_party/node/doc/contributing/maintaining/ |
D | maintaining-cjs-module-lexer.md | 30 * Follow the WASM build steps outlined in 32 This will generate the WASM based dist/lexer.js file.
|
/third_party/skia/specs/web-img-decode/ |
D | README.md | 16 It uses the CanvasKit WASM library under the hood to provide functionality, but
|
/third_party/skia/modules/canvaskit/npm_build/ |
D | README.md | 1 A WASM version of Skia's Canvas API. 38 WebPack's support for WASM is still somewhat experimental, but CanvasKit can be
|
/third_party/skia/experimental/tskit/ |
D | compile.sh | 78 -s WASM=1 \
|
/third_party/skia/experimental/wasm-skp-debugger/ |
D | README.md | 1 WASM SKP Debugger
|
D | compile.sh | 152 -s WASM=1 \
|
/third_party/skia/third_party/externals/imgui/examples/example_emscripten_wgpu/ |
D | Makefile | 37 LDFLAGS += -s WASM=1 -s ALLOW_MEMORY_GROWTH=1 -s NO_EXIT_RUNTIME=0 -s ASSERTIONS=1
|
/third_party/skia/third_party/externals/imgui/examples/example_emscripten_opengl3/ |
D | Makefile | 37 LDFLAGS += -s WASM=1 -s ALLOW_MEMORY_GROWTH=1 -s NO_EXIT_RUNTIME=0 -s ASSERTIONS=1
|
/third_party/skia/experimental/webgpu-bazel/src/ |
D | BUILD | 14 "-s WASM=1",
|
/third_party/rust/crates/memchr/bench/runs/2022-04-29_wasm-changes/ |
D | README.md | 10 These benchmarks were run after the initial [WASM PR] was merged. The main idea 11 here was to compare the non-WASM benchmarks before and after the PR merged to 12 ensure there were no serious regressions. Why test non-WASM? Because there 13 was some refactoring involved to add WASM support to the various dispatch 22 [WASM PR]: https://github.com/BurntSushi/memchr/pull/84
|
/third_party/skia/experimental/skottiekit/skottiekit/ |
D | README.md | 1 A WASM version of Skottie (Lottie with Skia).
|
/third_party/skia/experimental/skottiekit/ |
D | compile.sh | 208 -s WASM=1 \
|
1234