- 22 Jul, 2019 15 commits
-
-
Frank Tang authored
1. Fix formatToParts show "plusSign" for -0 by using signbit instead of < 0 2. Fix crash bug of formatToParts while notation is either "engineering" or "scientific". Bug: v8:9513 Change-Id: I36b0b995c157dc642b9c201694d0ac0bb0396988 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710148 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#62856}
-
Adam Klein authored
Previously, if the new length was less than the current length, we ignored the "configurable" value and set the length as requested. We already threw if the new length was greater than or equal to the current length. New behavior matches the spec and other implementations. Bug: v8:9460 Change-Id: Idb92fd121bdaa707f6abd2d2082628bbf3541b83 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709336Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#62855}
-
Ng Zhi An authored
Bug: v8:8460 Change-Id: I1d05e8a832d1b70f07c6782669c7b07764c7341d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1708454Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#62854}
-
Milad Farazmand authored
Port cd34523b Original Commit Message: 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. R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: Ia976d8017cacb61b46fe076c39ade6bc6137b7e9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1708989Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#62853}
-
Yang Qin authored
Added if statements to check if VECTOR_FACILITY are supported in order to avoid “illegal instruction” errors during SIMD tests on old s390 machines. Change-Id: I1ab841db02e6c47de54d4a15b973e5366f88e117 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704937Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#62852}
-
Yang Qin authored
Change-Id: I3541750049c4a17a294f819f278d69943565a2a0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1707933Reviewed-by:
-
Milad Farazmand authored
Port 4ca8b4dd Original Commit Message: This adds decoding and compilation of the "atomic.fence" operator, which is intended to preserve the synchronization guarantees of higher-level languages. Unlike other atomic operators, it does not target a particular linear memory. It may occur in modules which declare no memory, or a non-shared memory, without causing a validation error. See proposal: https://github.com/WebAssembly/threads/pull/141 See discussion: https://github.com/WebAssembly/threads/issues/140 R=mstarzinger@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG=v8:9452 LOG=N Change-Id: Ib8ad24e65154d7555a47e537f81110be47f4d4de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710620 Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#62850}
-
Clemens Hammacher authored
Instead of computing the jump table slot, and subtracting the start of the jump table, we can just compute the offset directly. This method is then used to compute jump table slots. R=titzer@chromium.org Change-Id: I634e5ee71a0d2e9d0d2db0ea373f833df91fba8e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709419Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#62849}
-
Ben L. Titzer authored
TBR=clemensh@chromium.org No-Try: true Change-Id: I993955063432cceedc6ef6fc1a999c8f2256279f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710668Reviewed-by:
-
Ben L. Titzer authored
This is a reland of bc33f5ae Original change's description: > Reland "[arraybuffer] Rearchitect backing store ownership" > > This is a reland of 31cd5d83 > > Original change's description: > > [arraybuffer] Rearchitect backing store ownership > > > > This CL completely rearchitects the ownership of array buffer backing stores, > > consolidating ownership into a {BackingStore} C++ object that is tracked > > throughout V8 using unique_ptr and shared_ptr where appropriate. > > > > Overall, lifetime management is simpler and more explicit. The numerous > > ways that array buffers were initialized have been streamlined to one > > Attach() method on JSArrayBuffer. The array buffer tracker in the > > GC implementation now manages std::shared_ptr<BackingStore> pointers, > > and the construction and destruction of the BackingStore object itself > > handles the underlying page or embedder-allocated memory. > > > > The embedder API remains unchanged for now. We use the > > v8::ArrayBuffer::Contents struct to hide an additional shared_ptr to > > keep the backing store alive properly, even in the case of aliases > > from live heap objects. Thus the embedder has a lower chance of making > > a mistake. Long-term, we should move the embedder to a model where they > > manage backing stores using shared_ptr to an opaque backing store object. > > > > R=mlippautz@chromium.org > > BUG=v8:9380,v8:9221 > > > > Change-Id: I48fae5ac85dcf6172a83f252439e77e7c1a16ccd > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1584323 > > Commit-Queue: Ben Titzer <titzer@chromium.org> > > Reviewed-by: Ben Titzer <titzer@chromium.org> > > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > > Reviewed-by: Yang Guo <yangguo@chromium.org> > > Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> > > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#62572} > > Bug: v8:9380, v8:9221 > Change-Id: If3f72967a8ebeb067c0edcfc16ed631e36829dbc > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1691906 > Commit-Queue: Ben Titzer <titzer@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62809} Bug: v8:9380, v8:9221 Change-Id: I9a2525753ae2424108d074fa81df5f25d945c824 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709409 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Mike Stanton authored
In serialization for concurrent TurboFan, we need to fully consume context chains to the root. This interferes with existing protections, firing the assert IsBootstrappingOrValidParentContext if the chain is queried to root. Instead, use unchecked_previous(). Bug: v8:7790 Change-Id: Id69885570fb88486c2f292023509bb02413a8ac5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710666Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#62846}
-
Darius Mercadier authored
A few methods (Free, TryFindInNode, SearchForNodeInList) were identical in each FreeList implementation, yet redefined each time. They are now defined in the class FreeList, and inherited by subclasses (which can override them if needed). Additionnaly, GuaranteedAllocatable in FreeListFast and FreeListMany were wrong in their respective last case; they are now fixed. Consequently to fixing FreeListMany::GuaranteedAllocatable, FreeListMany was slightly reworked: - The last freelist is now fully searched during allocation (rather than just looking at its first element like for the other freelists). Bug: v8:9329 Change-Id: Ic86ade3b1acaa2ca91cce17bd6822ec12aa594d9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706478Reviewed-by: -
Michael Achenbach authored
This adds a simple test calling: generate-bytecode-expectations --check-baseline It's added on one CQ and one CI builder. The infra side specifying the command line landed here: https://crrev.com/c/1709454 For the command to succeed on swarming we instruct the isolate server to archive the executable alongside with all the *.golden files needed for the --check-baseline command. Bug: v8:9520 Change-Id: I358ca7a7142c0fdaa7f6960515e524729a481394 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709424Reviewed-by:
Dan Elphick <delphick@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#62844}
-
Yu Yin authored
port 4ca8b4dd https://crrev.com/c/1701856 Original Commit Message: This adds decoding and compilation of the "atomic.fence" operator, which is intended to preserve the synchronization guarantees of higher-level languages. Unlike other atomic operators, it does not target a particular linear memory. It may occur in modules which declare no memory, or a non-shared memory, without causing a validation error. See proposal: https://github.com/WebAssembly/threads/pull/141 See discussion: https://github.com/WebAssembly/threads/issues/140 Change-Id: Ia60d58a6bf58e8236591d515d30184418cee47c5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710337Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/be534da..1e5d7d6 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I92597bcfcc7e9ff402fd3bfcb3dd64816374eafc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709075Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#62842}
-
- 21 Jul, 2019 2 commits
-
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/0137a33..1a411f7 [spec] Fix header level (#1047) (Andreas Rossberg) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/1a411f7 TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: I86898b7e902aed9af7727b390c2a9ca0419afc28 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1711313Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/bcbed09..be534da Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/5075be9..53913ce Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/0a0fbf1..ee7b9dd Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/3e2c753..f485a21 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: Id42610f92bd1730b16f9c9f3156e504ae672a031 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709177Reviewed-by:
-
- 20 Jul, 2019 3 commits
-
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/666dc4c..0137a33 [interpreter] Fix typo in comment (#1045) (NDTSTN) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/0137a33 TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: Ic5392b5f1efcd93f4f856787204f30c81b88beaa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1708698Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/c986429..bcbed09 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/7b7a5c0..67b293c Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/42a883d..5075be9 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/f4e0cc6..0a0fbf1 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/558ca3e..3e2c753 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: Ia20af6ec0c7b23b4361c33dd4c5a820be023ee10 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709307Reviewed-by:
-
Ng Zhi An authored
The bytes was accidentally mixed up when disasm for pand got added in https://crrev.com/c/907489. Change-Id: If5595f00356c20c5c9d9e9a0fb43f7ea853b2941 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710329 Auto-Submit: Zhi An Ng <zhin@chromium.org> Reviewed-by:
-
- 19 Jul, 2019 20 commits
-
-
Frank Tang authored
Bug: v8:9523 Change-Id: Ib9d6772d2025b0452ddcd777cc777276f9038e97 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710960Reviewed-by:
-
Sam Clegg authored
All the whitespace checks need to be disabled because we use 2-space indentation. One day this could become part of a presubmit but for now its useful simply to be able to run the flake8 tools directly on a file in the v8 repo. Change-Id: I9d7ede102aaa17a7c6e7bf29887565ea2deeb887 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1697055Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Sam Clegg <sbc@chromium.org> Cr-Commit-Position: refs/heads/master@{#62835}
-
Frank Tang authored
1. Sync with https://github.com/tc39/proposal-unified-intl-numberformat/pull/57 so the formatting of {style: "unit" unit: "percent"} and the formatting of {style: "percent:"} are treated different that simplified the algorithm. 2. Store style into bit flags because we need it quickly during format. 3. Add more unit tests and regression test. Bug: v8:9498 Change-Id: I75ed22fef1feb73ebf624bda70ebe45b80e7bc8b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1704948Reviewed-by:
-
Dan Elphick authored
Fix CheckBaselineExpectations returning 2 when it can't read its input file. Since this was originally just in main, convert it to std::exit. Change-Id: I70ae6fbc6e5e12b748d2ab1cc83b1deb67a8f861 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1710659 Auto-Submit: Dan Elphick <delphick@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#62833}
-
Dan Elphick authored
In InterpreterCollectSourcePositions tests always unset FLAG_stress_lazy_source_positions as the tests cannot work with it due to assuming that source positions won't be collected immediately after a normal compile. Bug: v8:8510 Change-Id: I194ed06c59336f5af3b7b2113a12c1a21dd6bcac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709425 Commit-Queue: Dan Elphick <delphick@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
-
Ulan Degenbaev authored
Bug: chromium:677883 Change-Id: Id28310da0eb8762f30927397c9eaa942ac74852a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709417Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#62831}
-
Yang Guo authored
Adds a new out param which allows accessing the ScriptOrModule of a function, which allows an embedder such as Node.js to use the function's i::Script lifetime. Refs: https://github.com/nodejs/node-v8/issues/111 Change-Id: I34346d94d76e8f9b8377c97d948673f4b95eb9d5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1699698Reviewed-by:
-
Toon Verwaest authored
This is a reland of e55e0aa5 Original change's description: > [runtime] Fix protector invalidation > > Protectors trigger when special properties are modified or masked. Previously > we would check whether the property stored on the holder would invalidate the > protector. Stores to to the receiver rather than the holder, however, so this > CL changes holder for receiver, and adds additional checks that were missing. > > Bug: v8:9466 > Change-Id: I81bc3d73f91381da0d254e9eb79365ae2d25d998 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1708468 > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62805} Tbr: leszeks@chromium.org Bug: v8:9466 Change-Id: I693c73577ca9a35a271f509770cc1c87e5cc4b73 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709420 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#62829}
-
Clemens Hammacher authored
Those helped investigating a surprisingly long delay in wasm code caching. R=titzer@chromium.org CC=bbudge@chromium.org Change-Id: Id5491b9cb8824f337c20f66d5ab26f94d1a53562 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709418Reviewed-by:
-
Michael Lippautz authored
Adds global allocation limit to the general overshoot safety net for triggering GC. Adds a check to the interrupt that is triggered by the embedder to catch cases where there's no on-heap allocation. Bug: chromium:985641, chromium:948807 Change-Id: I3bc0c30f9344b57096db7ebbd8ad8c76808548ba Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709414Reviewed-by:
-
Michael Starzinger authored
This makes sure the language mode of the module is correctly propagated through the WebAssembly module, so that exported functions are allocated with the correct language mode. It extends the existing {ModuleOrigin} enum to consist of three values now. R=clemensh@chromium.org TEST=mjsunit/regress/wasm/regress-985154 BUG=chromium:985154 Change-Id: Id7b566738b1e710cc5001b894022bcd0f2c01bc3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1708484 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
-
Dan Elphick authored
Add a new mode to generate-bytecode-expectations to be used in a coming test that tests that the bytecode expectations generated by --rebaseline match the current state. Change-Id: Ic03787cd853f9bf7d9b4412f96a767036c848c61 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1708477 Auto-Submit: Dan Elphick <delphick@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#62825}
-
Sathya Gunasekaran authored
This reverts commit c2ee4a79. Reason for revert: webgl_conformance_tests deqp/data/gles2/shaders/conversions.html crashes on Android FYI Release (Nexus 9) See https://bugs.chromium.org/p/chromium/issues/detail?id=985624 Original change's description: > Reland "[regexp] Call the regexp interpreter without CEntry overhead" > > This is a reland of d4d28b73 > > Original change's description: > > [regexp] Call the regexp interpreter without CEntry overhead > > > > Previously all RegExp calls went through Runtime_RegExpExec when --regexp-interpret-all was set. > > > > This CL avoids the runtime overhead by calling into the interpreter directly from the RegExpExec Builtin when the regular expression subject was already compiled to ByteCode (i.e. after the first call). > > > > Bug: v8:8954 > > Change-Id: Iae9dfcef3370b772a05b2942305335d592f6f15a > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1698391 > > Commit-Queue: Patrick Thier <pthier@google.com> > > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#62753} > > Bug: v8:8954 > Change-Id: I1f0b6de9c6da65bcb582ddb41a37419116a5c510 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1706053 > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Commit-Queue: Patrick Thier <pthier@google.com> > Cr-Commit-Position: refs/heads/master@{#62794} TBR=jgruber@chromium.org,petermarshall@chromium.org,pthier@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:8954, chromium:985624 Change-Id: I5bc2c397a09979f42f28670f80a5366f2a33d80f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709411 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
-
Dan Elphick authored
Fix a cctest/test-bytecode-generator/PrivateMethods mismatch between the PrivateMethods source string and the snippet in the golden file due to missing newline at the end of the string. Change C++ raw string back to a normal string since in this case it makes it harder to see the problem. Change-Id: I3bea8873d37fbacac65548be8261f6b04104132f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709413 Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
This was introduced in https://crrev.com/c/1703762. R=titzer@chromium.org CC=zhin@chromium.org Change-Id: I3f13ab1ea1e87a2615883aa441581c62166f3587 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709412Reviewed-by:
-
Michael Starzinger authored
This adds decoding and compilation of the "atomic.fence" operator, which is intended to preserve the synchronization guarantees of higher-level languages. Unlike other atomic operators, it does not target a particular linear memory. It may occur in modules which declare no memory, or a non-shared memory, without causing a validation error. See proposal: https://github.com/WebAssembly/threads/pull/141 See discussion: https://github.com/WebAssembly/threads/issues/140 R=clemensh@chromium.org TEST=cctest/test-run-wasm-atomics/RunWasmXXX_AtomicFence BUG=v8:9452 Change-Id: Ibf7e46227f7edfe5c81c097cfc15924c59614067 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1701856 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
Every time we clang-format this list, one more element gets stripped off into its own line. Fix this by disabling clang-format for this chunk (we did the same for the chunk below). R=mstarzinger@chromium.org Change-Id: I49efdccc78eb4186cdb15513600594d539082fd0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1708478Reviewed-by:
-
Frank Tang authored
Sync with https://github.com/tc39/proposal-unified-intl-numberformat/pull/54 Bug: v8:9483 Change-Id: I2aec5a78be235bddd4faa568665b73b9b84d7c93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1700426Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#62819}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/fb75973..c986429 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/f8c5b19..42a883d Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/9217ff8..f4e0cc6 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/29ddc91..558ca3e TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I6e01c52d33ed9745dcfc170d829fa31545368ec1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1709112Reviewed-by:
-
Ng Zhi An authored
Bug: v8:8460 Change-Id: I3e649e1398be429b8aff5b57316e320f9ca5ae8f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1703763 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by:
-
