- 28 Apr, 2022 1 commit
-
-
Andreas Haas authored
The SIMD proposal has been merged into the main spec, it is not necessary anymore to execute the SIMD proposal tests additionally. R=gdeepti@chromium.org Change-Id: I1c5847a1bfba2d0c956cf353816fd71417506a1f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3609848Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#80241}
-
- 15 Mar, 2022 1 commit
-
-
Clemens Backes authored
It turned out that on arm and arm64 we over-estimated the code size of a Wasm module quite a bit. This CL adds some more output for the --trace-wasm-compilation-times flag, and adds a script to compute the factors we use for code size estimates from that output. I ran the script on a few benchmarks (an older Epic module, the current Photoshop module, and the benchmark from the linked bug), and adjusted the constants accordingly. Also, simplify the API of {ReservationSize} to only return a single number, and fail internally if we need to allocate more than the engine supports (which would only fail for artificially large modules). R=jkummerow@chromium.org Bug: chromium:1302310 Change-Id: I5b2c27ff3e360fb6738cf5dd697bcee09e106b6d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3522067Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#79482}
-
- 14 Sep, 2021 1 commit
-
-
Andreas Haas authored
WPT and WebAssembly spec tests are not 100% in sync, which means that there are aspects of the WebAssembly spec that get only tested by WPT. Up until now WPT was only executed on the blink side, and failing tests were just ignored. With this CL we add WPT to the existing wasm spec test setup, so that we run both the spec tests, and WPT. Bug: v8:12227 Change-Id: Iccbe696a6d9dd01f8bab1990736f1ed16e0cdf7b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3160347Reviewed-by: Liviu Rau <liviurau@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#76823}
-
- 17 Mar, 2021 1 commit
-
-
Andreas Haas authored
The bulk-memory proposal and the reference types proposal have been merged into the main repository, so we don't have to run the proposal tests anymore. R=ecmziegler@chromium.org Change-Id: I14583b8c1c387075442a402458ce04e7c6071f89 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2752165 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Emanuel Ziegler <ecmziegler@chromium.org> Cr-Commit-Position: refs/heads/master@{#73481}
-
- 24 Feb, 2021 2 commits
-
-
Thibaud Michaud authored
This reverts commit 1db61fb3. Reason for revert: https://ci.chromium.org/ui/p/v8/builders/ci/V8%20Linux%20-%20debug/34083/overview Original change's description: > [wasm][eh] Stage exception handling > > This was staged through a back-merge in v8.9. Also stage it for the > upcoming v9.0 release. > > R=ahaas@chromium.org > > Bug: v8:8091 > Change-Id: Ie9e6d25bbc5d428e5c9128345209f95f2078b733 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2715524 > Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#73013} Bug: v8:8091 Change-Id: I18b9706e8aab4883a3d3c120a6cd06e7232aecf7 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2718148 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#73016}
-
Thibaud Michaud authored
This was staged through a back-merge in v8.9. Also stage it for the upcoming v9.0 release. R=ahaas@chromium.org Bug: v8:8091 Change-Id: Ie9e6d25bbc5d428e5c9128345209f95f2078b733 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2715524 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#73013}
-
- 08 Feb, 2021 1 commit
-
-
Clemens Backes authored
Update the wasm spec tests to include the memory64 proposal. Some tests are failing currently because of broken spec tests or missing v8 support. This will be addressed in follow-up CLs. R=ahaas@chromium.org CC=zhin@chromium.org Bug: v8:11401 Change-Id: I1a8f75e70f9d0828ad32c960c113f5e4c0d1a44b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2679683 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#72561}
-
- 01 Dec, 2020 1 commit
-
-
Clemens Backes authored
The wasm fuzzer corpus is pretty outdated. The script that was used to generate it did not work any more. This CL updates the script, and runs it. This generates a fuzzer corpus of 42011 wasm modules, compared to 15290 before. The new modules will contain new features like SIMD and multi-value, which will be interesting fuzzer inputs. R=ahaas@chromium.org Change-Id: Ic3df26930cb8c1c6e8d521597ceb06cc338c02ed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2565512Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71537}
-
- 10 Sep, 2020 1 commit
-
-
Ng Zhi An authored
This reverts commit e8976cf9. Reason for revert: Mark f32x4_cmp as fail, lowering is not fully implemented yet. Original change's description: > Revert "[wasm-simd] Stage SIMD" > > This reverts commit 1d2726dd. > > Reason for revert: ODROID failure: https://ci.chromium.org/p/v8/builders/ci/V8%20Arm%20-%20debug/15814? > > Original change's description: > > [wasm-simd] Stage SIMD > > > > SIMD has been pretty stable for a while now, we are not expecting big > > changes (like opcode renumbers), there might be new instructions added, > > and they will all be backwards-compatible. > > > > The reference interpreter in the SIMD proposal is now capable of > > generating JS files for all test cases, so we can now run them. > > > > There is a bit of tweaking necessary, since SIMD tests are in > > tests/core/simd subfolder in the spec, so we need to change the glob > > into a find that will traverse into subdirectory. > > > > Bug: v8:10835 > > Change-Id: I1f7e3cf37f21b2aa2537d1e34242da2373bbf626 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2378587 > > Commit-Queue: Zhi An Ng <zhin@chromium.org> > > Reviewed-by: Andreas Haas <ahaas@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#69793} > > TBR=bbudge@chromium.org,ahaas@chromium.org,zhin@chromium.org > > Change-Id: I3a90c616109ca048691d97ab45698bc15a678e18 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: v8:10835 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2402379 > Reviewed-by: Shu-yu Guo <syg@chromium.org> > Commit-Queue: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#69794} TBR=bbudge@chromium.org,ahaas@chromium.org,zhin@chromium.org,syg@chromium.org # Not skipping CQ checks because this is a reland. Bug: v8:10835 Change-Id: I3d87dd2adba6ada2ec3ebf5e13bff378a74b03e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2402386Reviewed-by: Zhi An Ng <zhin@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#69817}
-
- 09 Sep, 2020 2 commits
-
-
Shu-yu Guo authored
This reverts commit 1d2726dd. Reason for revert: ODROID failure: https://ci.chromium.org/p/v8/builders/ci/V8%20Arm%20-%20debug/15814? Original change's description: > [wasm-simd] Stage SIMD > > SIMD has been pretty stable for a while now, we are not expecting big > changes (like opcode renumbers), there might be new instructions added, > and they will all be backwards-compatible. > > The reference interpreter in the SIMD proposal is now capable of > generating JS files for all test cases, so we can now run them. > > There is a bit of tweaking necessary, since SIMD tests are in > tests/core/simd subfolder in the spec, so we need to change the glob > into a find that will traverse into subdirectory. > > Bug: v8:10835 > Change-Id: I1f7e3cf37f21b2aa2537d1e34242da2373bbf626 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2378587 > Commit-Queue: Zhi An Ng <zhin@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Cr-Commit-Position: refs/heads/master@{#69793} TBR=bbudge@chromium.org,ahaas@chromium.org,zhin@chromium.org Change-Id: I3a90c616109ca048691d97ab45698bc15a678e18 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:10835 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2402379Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/master@{#69794}
-
Ng Zhi An authored
SIMD has been pretty stable for a while now, we are not expecting big changes (like opcode renumbers), there might be new instructions added, and they will all be backwards-compatible. The reference interpreter in the SIMD proposal is now capable of generating JS files for all test cases, so we can now run them. There is a bit of tweaking necessary, since SIMD tests are in tests/core/simd subfolder in the spec, so we need to change the glob into a find that will traverse into subdirectory. Bug: v8:10835 Change-Id: I1f7e3cf37f21b2aa2537d1e34242da2373bbf626 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2378587 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#69793}
-
- 02 Jul, 2020 1 commit
-
-
Thibaud Michaud authored
R=ahaas@chromium.org Bug: v8:7431 Change-Id: Ie416ea6048ffed792225822b053aa3ed37aa4919 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2278468Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#68658}
-
- 25 Jun, 2020 1 commit
-
-
Andreas Haas authored
The BigInt proposal got to stage 4 and integrated into the main spec. Therefore the proposal tests are unnecessary and will be outdated soon. R=thibaudm@chromium.org Change-Id: I149de015f098a89333dd907bf5a4d18a36086c2b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2264095Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#68542}
-
- 25 May, 2020 1 commit
-
-
Andreas Haas authored
This CL also fixes a small bug in the update-wasm-spec-tests.sh script, as it was not able to handle proposals without additional core spec tests. It also disables a lot of tests. R=jkummerow@chromium.org bug:v8:10556 Change-Id: Ibd885350478de935dc67edb664715cfa64f1d8e1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2210248 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#67949}
-
- 22 Apr, 2020 1 commit
-
-
Thibaud Michaud authored
The multi-value proposal is now merged in the main spec repository, so: - Remove everything that references the multi-value spec repository - Add --experimental-wasm-mv to the default flags R=ahaas@chromium.org Change-Id: I9f809c21404bb5c1d21eb330748ea51a15688546 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2153219 Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#67313}
-
- 22 Oct, 2019 1 commit
-
-
Thibaud Michaud authored
R=mstarzinger@chromium.org Bug: v8:6672 Change-Id: Id8a53f6f74fa05150469c35ceba9470e75363637 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1847156Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#64472}
-
- 05 Sep, 2019 1 commit
-
-
Andreas Haas authored
There was no problem with the original CL. I just had a problem with my local git branches. Original message: The implementation on wasm-bigint has been done, as far as I can tell. There are no spec tests yet, only an out-dated copy of the original spec tests which don't pass anymore. Therefore I disabled all the tests for now and created a tracking bug at https://crbug.com/v8/9673. TBR=adamk@chromium.org Bug: v8:7741, v8:9673 Change-Id: Ida7ccda4547cf3fdcdff151d8b02946b7aa534ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1787420Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#63575}
-
- 28 Aug, 2019 2 commits
-
-
Michael Starzinger authored
R=ahaas@chromium.org BUG=v8:7742 Change-Id: Ifaab43b3ca25eb3e03b7f02a2a3864ecc3f41d61 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1771791Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#63425}
-
Andreas Haas authored
At the moment we only run the js-api spec tests of the core API on our try bots. With the new staging process we want to introduce for WebAssembly language features, see https://docs.google.com/document/d/1hB8mpWmzmtaxZ8PuJEkAWLwFqXTjrw7mJ3Ge9W1dB4E, we also want to run the js-api spec tests of proposals for which we already staged the implementation. With this CL I do the following changes: 1) The tools/wasm/update-wasm-spec-tests.sh now copies the js-api spec tests of the main spec and of the proposals to test/wasm-js/tests, and then uploads this directory to google cloud storage. The main spec tests are in test/wasm-js/tests, the proposal tests are in test/wasm-js/tests/proposals/PROPOSAL_NAME/. 2) Adjust the test-runner in test/wasm-js to run tests in tests/* instead of data/test/js-api/*. Thereby it also runs the proposal tests in test/wasm-js/tests/proposals/PROPOSAL_NAME/. For the proposal tests, the test runner now also adds d8 flags. 3) Remove the dependency to https://github.com/WebAssembly/spec from DEPS. 4) Cleanup .gitignore and wasm-js.status 5) Disable spec tests we don't pass with the new proposal. R=tmrts@chromium.org Bug: v8:9653 Change-Id: Ib3420871f17cb146d6cc7868f5613942a7f79d84 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1768372 Commit-Queue: Tamer Tas <tmrts@chromium.org> Reviewed-by: Tamer Tas <tmrts@chromium.org> Cr-Commit-Position: refs/heads/master@{#63419}
-
- 17 Jul, 2019 1 commit
-
-
Andreas Haas authored
With this CL we add proposal tests to the wasm-spec-tests. For this I extended the update-wasm-spec-tests.sh script. Additionally to generating the spec tests it does the following: For each proposal it identifies those tests that are different to the spec tests, and then copies those tests also to the wasm-spec-tests directory. Additionally I adjusted the test runner of the wasm spec test to run the proposal tests with the correct flags. CC=binji@chromium.org R=clemensh@chromium.org Bug: v8:7581 Change-Id: Idb7aa3c0a468ddb65b2ef3421def836561579cd9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706470Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#62777}
-
- 22 Nov, 2018 1 commit
-
-
Ben L. Titzer authored
Add a profiler for functions imported to WASM instances. This profiler is implemented entirely in JavaScript and monkey-patches WebAssembly.instantiate() and new WebAssembly.Instance() to instrument the imported functions to each instance in order to count their invocations and cumulative time. R=mstarzinger@chromium.org Bug: v8:8423 Change-Id: If456355aba07dc69c5500bafbe35fc56b31486af Reviewed-on: https://chromium-review.googlesource.com/c/1347488 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#57746}
-
- 18 Oct, 2018 1 commit
-
-
Ben Smith authored
This is a reland of a12203c6 Original change's description: > [wasm] Add a new wasm-js testsuite to run js-api tests > > These changes were necessary to run with the new style of jsapi tests > introduced in https://github.com/WebAssembly/spec/pull/883. > > Change-Id: I4629dd48d595ed97ed0607dec9e7d9808c706a7e > Reviewed-on: https://chromium-review.googlesource.com/c/1277724 > Commit-Queue: Ben Smith <binji@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Mathias Bynens <mathias@chromium.org> > Cr-Commit-Position: refs/heads/master@{#56745} Change-Id: I25fcd95bfc1aee1d21da390359423e5dfed112a4 Reviewed-on: https://chromium-review.googlesource.com/c/1286952 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#56791}
-
- 17 Oct, 2018 2 commits
-
-
Bill Budge authored
This reverts commit a12203c6. Reason for revert: Breaks isolate_tests https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Linux%20-%20builder/36777 Original change's description: > [wasm] Add a new wasm-js testsuite to run js-api tests > > These changes were necessary to run with the new style of jsapi tests > introduced in https://github.com/WebAssembly/spec/pull/883. > > Change-Id: I4629dd48d595ed97ed0607dec9e7d9808c706a7e > Reviewed-on: https://chromium-review.googlesource.com/c/1277724 > Commit-Queue: Ben Smith <binji@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Mathias Bynens <mathias@chromium.org> > Cr-Commit-Position: refs/heads/master@{#56745} TBR=binji@chromium.org,machenbach@chromium.org,yangguo@chromium.org,ahaas@chromium.org,clemensh@chromium.org,mathias@chromium.org Change-Id: I2edd0ca94cb5990322571879c81671fa835f3ecd No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/1286526Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#56746}
-
Ben Smith authored
These changes were necessary to run with the new style of jsapi tests introduced in https://github.com/WebAssembly/spec/pull/883. Change-Id: I4629dd48d595ed97ed0607dec9e7d9808c706a7e Reviewed-on: https://chromium-review.googlesource.com/c/1277724 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#56745}
-
- 25 Jan, 2018 1 commit
-
-
Andreas Haas authored
In addition I added some comments in the update script which describes steps which have to be takes the first time you run the script on a new machine. R=titzer@chromium.org Change-Id: Ib360e6fcdcb63eaf225f398eff60041b48f86b62 Reviewed-on: https://chromium-review.googlesource.com/883344Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#50863}
-
- 08 Dec, 2017 1 commit
-
-
Andreas Haas authored
I also adjusted the update script because the output directory of the run.py script we call has changed. R=clemensh#chromium.org Change-Id: I432c81f1a2ffd3c96a294f771064672f7edad250 Reviewed-on: https://chromium-review.googlesource.com/817275Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#49968}
-
- 10 Oct, 2017 1 commit
-
-
Andreas Haas authored
R=titzer@chromium.org Change-Id: Ie65c03347b0619a107bc06725ce587e0270fa9a1 Reviewed-on: https://chromium-review.googlesource.com/707102 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#48425}
-
- 21 Jun, 2017 1 commit
-
-
Andreas Haas authored
The fuzzer has already been removed from chromium. In addition I removed code which was only used by this fuzzer. BUG=chromium:734550 R=clemensh@chromium.org CC=mstarzinger@chromium.org Change-Id: I2ff4614e4d64131412ead759318e5c38e38f5d3d Reviewed-on: https://chromium-review.googlesource.com/542816 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#46078}
-
- 09 Jun, 2017 1 commit
-
-
Clemens Hammacher authored
This CL removes most occurences of "WASM" from outputs and comments in the code. They are replaced either by "WebAssembly" or (especially in comments) "wasm". These are the spellings officially proposed on http://webassembly.org/. R=ahaas@chromium.org BUG=v8:6474 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Id39fa5e25591678263745a4eab266db546e65983 Reviewed-on: https://chromium-review.googlesource.com/529085Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#45824}
-
- 02 Jun, 2017 1 commit
-
-
Andreas Haas authored
This CL updates the hook for the WebAssembly spec repository, and it updates the WebAssembly spec tests. The WebAssembly spec tests have to be updated manually with the tools/wasm/update-wasm-spec-tests.sh script. Mircea, I saw that you updated the WebAssembly spec repository last time. Can you please take a look? UPDATE: I improved the update script slightly, and there is one additional JS API test we fail now and have to fix eventually. R=mtrofin@chromium.org Change-Id: I3c0df9cee64d444147db47daa0c1936edf116173 Reviewed-on: https://chromium-review.googlesource.com/509257Reviewed-by: Mircea Trofin <mtrofin@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#45692}
-
- 28 Apr, 2017 1 commit
-
-
Andreas Haas authored
The current test/fuzzer/wasm directory is used for two things: 1) as the corpus directory for clusterfuzz 2) to test in v8 that the fuzzer runs correctly. With the newly added files from the wasm spec tests this directory grew quite big and adds unnecessary load on the trybots. Therefore I want to do the following steps: 1) In this CL for V8: create a new directory for the clusterfuzz corpus 2) In chromium: use the new corpus directory 3) In v8: clean up the old directory to use it on the trybots. R=bradnelson@chromium.org CC=mmoroz@chromium.org Change-Id: If690022558bb5780edf5a3649fb9745ef9c7407a Reviewed-on: https://chromium-review.googlesource.com/490367 Commit-Queue: Brad Nelson <bradnelson@chromium.org> Reviewed-by: Brad Nelson <bradnelson@chromium.org> Cr-Commit-Position: refs/heads/master@{#44991}
-
- 27 Apr, 2017 1 commit
-
-
Andreas Haas authored
I moved the wasm update scripts from tools/ to tools/wasm. In addition I cleaned up the scripts a bit. R=machenbach@chromium.org Change-Id: I545dd556712e272e6509b78e343e9063346abe56 Reviewed-on: https://chromium-review.googlesource.com/488601Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#44940}
-