- 10 Dec, 2019 10 commits
-
-
Michael Achenbach authored
This reverts commit c924f54e. Reason for revert: Suspect for GPU failures: https://ci.chromium.org/p/v8/builders/ci/Linux%20V8%20FYI%20Release%20(NVIDIA)/7641 Original change's description: > [turbofan][ptr-compr] Remove redundant ChangeTaggedToCompressed > > The final goal is to eliminate it altogether. This CL just > eliminate the redundant ones. > > Bug: v8:7703 > Change-Id: If6e718c373fca7c65ce46c347533ec4550fbc444 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1950968 > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65398} TBR=tebbi@chromium.org,solanes@chromium.org Change-Id: Id280d7b0a850e3aacd56f839a0fc36d02a88f34c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7703 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1960286Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#65403}
-
Georg Neis authored
Change-Id: Ie0b6e7876abe229915afa4aaf3b1692750254cbc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1950977Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#65402}
-
Liviu Rau authored
Change-Id: I00a1cd9c74f6f58b89e35068721dbc30abf396e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955732Reviewed-by:
-
Georg Neis authored
- Move {function_} and {closure_hints_} out of each {Environment}, as it's sufficient to only have it in the serializer class. - Similarly, remove {parameter_count_} and {register_count_} from {Environment}. To accomodate for that, change implementation of "dead" environments to be based on a flag. - Remove {ClearEphemeralHints}. This was called for any bytecode not recognized by the serializer. I think it makes more sense to just do nothing at all for those, i.e. keep whatever hints we have. - Split the magical {ephemeral_hints_} vector into three separate things for clarity: {accumulator_hints_}, {parameters_hints_}, and {locals_hints}. Note that we already had {current_context_hints_}. Bug: v8:7790 Change-Id: Icbe33f500bdbd0f8002570934f59425f49c9de12 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958010 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#65400}
-
Georg Neis authored
- Remove CLEAR_ENVIRONMENT_LIST of bytecodes, since clearing the environment is already the default behavior. - Address a TODO in Environment::Merge: also merge context hints. - Don't needlessly clear register hints for InvokeIntrinsic. Bug: v8:7790 Change-Id: Ibead921002e45ed46c8c1629cae7bb9febf09b90 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1952870Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Reviewed-by:
-
Santiago Aboy Solanes authored
The final goal is to eliminate it altogether. This CL just eliminate the redundant ones. Bug: v8:7703 Change-Id: If6e718c373fca7c65ce46c347533ec4550fbc444 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1950968Reviewed-by:
-
Tobias Tebbi authored
This CL generalizes and improves how we handle allocations in Torque. Overview of the changes: - Remove obsolete special handling for JSObject classes, since it was incomplete: It breaks as soon as slack tracking is active. - Handle array initialization using slices. - Properly align allocation sizes. This enabled allocating strings. - Port AllocateSeq{One,Two}ByteString to Torque, which is much easier now than the old CSA code since allocation size alignment and large-object space allocation just happen out-of-the-box. - Remove obsolete or unnecessary intrinsics, some of them turn into macros in the torque_internal namespace. - Distinguish between header size and overall size for ClassType, make size optional and only defined when it is statically known. Bug: v8:10004 v8:7793 Change-Id: I623db233e7fb4deed54e8039ae0c24705e9a44e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1932356Reviewed-by:Nico Hartmann <nicohartmann@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#65397}
-
Michael Achenbach authored
Deprecation was prepared by: https://crrev.com/c/1899774 Bug: v8:9941 Change-Id: Idf236c2ebfc23e26dcb264747721d7c18986b6b8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955552Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#65396}
-
Leszek Swirski authored
Add HeapObject overloads for MarkingBarrier, GenerationalBarrier and WriteBarrierForCode, which the compiler automatically prefers if a setter's type is a subclass of HeapObject. These overloads can skip the IsHeapObject check, providing maybe a small performance boost and I measure a ~4.5kB binary size reduction in libv8.so Change-Id: Ia65ff8425ae4895da406587101c7813fe6bf5a2b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958055 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Simon Zünd authored
Bug: v8:10021 Change-Id: Ieffa39c09e028b9c0f91f1823ea6e89f81fec4cb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1948707 Commit-Queue: Simon Zünd <szuend@chromium.org> Auto-Submit: Simon Zünd <szuend@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#65394}
-
- 09 Dec, 2019 18 commits
-
-
Bartek Nowierski authored
NOTE! This re-introduces the following change with a modification that detached_window_time_in_seconds is initialized with 0, instead of current time. https://chromium-review.googlesource.com/c/v8/v8/+/1924000 Bug: chromium:1018156 Change-Id: I6d0880e0355d2cb08dbf4f2ef92c8fcead03f9ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958344Reviewed-by:
-
Milad Farazmand authored
The API thread_cputime() is only defined but not yet implemented on IBMi. Change-Id: I8ea7ff724e749f537b54e75a00d718500807ca8a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1957831Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#65392}
-
Leszek Swirski authored
We use the compilation entry point as a caching scope for deserializing lookups, to avoid redundantly iterating over parent scopes when accessing the same variable multiple times. However, this caching scope messes with lookups that are looking for lexical name conflicts, as opposed to just resolving variables. In particular, it messes with name conflict lookups and sloppy block function hoisting checks, when there are other scopes in the way, e.g. function f() { let x; try { throw 0; } catch (x) { // This catch is the entry scope // Naive use of caches will find the catch-bound x (which is // a VAR), and declare 'no conflict'. eval("var x;"); // Naive use of caches will find the catch-bound x (which is // a VAR), and determine that this function can be hoisted. eval("{ function x() {} }"); } } Previously, we worked around this by avoiding cache uses for these lookups, but this had the issue of instead caching the same variable multiple times, on different scopes. In particular, we saw: function f() { with ({}) { // This with is the entry scope, any other scope would do // though. // The conflict check on `var f` caches the function name // variable on the function scope, the subsequent 'real' // lookup of `f` caches the function name variable on the // entry i.e. with scope. eval("var f; f;"); } } With this patch, we change the caching behaviour to cache on the first non-eval declaration scope above the eval -- in the above examples, this becomes the parent function "f". For compilations with no intermediate non-decl scopes (no with or catch scopes between the function and eval) this becomes equivalent to the existing entry-point-based caching. This means that normal lookups do have to (sometimes) iterate more scopes, and we do have to be careful when using the cache to not use it for lookups in these intermediate scopes (a new IsOuterScope DCHECK guards against this), but we can now safely ignore the cache scope when doing the name-collision lookups, as they only iterate up to the outer non-eval declaration scope anyway. Bug: chromium:1026603 Bug: chromium:1029461 Change-Id: I9e7a96ce4b8adbc7ed47a49fba6fba58b526235b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955731 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: -
Leszek Swirski authored
This reverts commit 026a0c21. Reason for revert: Reverting due to https://crbug.com/1029461 Original change's description: > [parser] Fix variable caching for conflict lookup > > During conflict lookup (for lexical variables and sloppy block function > hoisting), we cache the looked-up variable on the current scope if the > lookup goes through a ScopeInfo. However, for variable lookup during > scope analysis, we use the "entry point" as the cache. > > Since both lookups can create Variables, this can cause us to create > duplicate variables, e.g. a duplicate function name variable in the > attached test. > > Instead, for ScopeInfo conflict lookups we can cache the result on the > function's outer scope, which shoud be equivalent to the entry point. > > As a (necessary) drive-by, we can terminate the lookup early if we find > a VAR with the same name, as we can safely assume that its existence > means that it doesn't conflict, which means that our variable can't > conflict either. > > Bug: chromium:1026603 > Change-Id: I19f80f65597ba6573ebe0b48aa5698f55e5c3ea1 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1928861 > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65138} TBR=leszeks@chromium.org,verwaest@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:1026603 Bug: chromium:1029461 Change-Id: Id7f5dd342e32e1bb57c51b3748feff32ee0ba41d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958014Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/4f02786..b1050d1 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/c3cb105..8953fbe TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: If375ec3ca9676c651ec7097a431e101aad5ff843 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955992Reviewed-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@{#65389}
-
Clemens Backes authored
This reverts commit c4cf2ea4. Reason for revert: Seems to cause more regressions than improvement. Let's see what the perf bots say about the revert. Original change's description: > [codegen] Remove redundant xorpd instructions > > It seems like they were originally added in https://crrev.com/23654026 > (Sep 2013) to break dependences in the OOO pipeline. This code pattern > was then later copied for other instructions too > (https://crrev.com/1424333002). > The reason for the xorpd is not mentioned in the code though, and I > found no other compiler doing this. So maybe it's obsolete by now, and > only increases code size. > > Let's remove them and see if we get any performance regressions. > > R=ahaas@chromium.org > CC=yangguo@chromium.org > > Change-Id: I0e6d65afa67f0ee286e5b0ba95c91092c5261c8f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1926427 > Reviewed-by: Yang Guo <yangguo@chromium.org> > Reviewed-by: Andreas Haas <ahaas@chromium.org> > Commit-Queue: Clemens Backes <clemensb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65077} TBR=yangguo@chromium.org,ahaas@chromium.org,clemensb@chromium.org Bug: chromium:1027876, chromium:1027449 Change-Id: I533729722e294dbe567222b1c4084df6b864d2ff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958053Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#65388}
-
Clemens Backes authored
Instead of using hard-coded clang flags (which are missing important flags and are thus not that useful), use the flags for some unrelated C++ file. R=ahaas@chromium.org No-Try: true Change-Id: I516df9431e8aad1a63e832aa28450475193fd404 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955549 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
-
Liviu Rau authored
No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: Iae100d8f9676f2f387d915ab6e70fa31d7ad30af Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955551 Commit-Queue: Liviu Rau <liviurau@chromium.org> Reviewed-by:
-
Dominik Inführ authored
Before this CL a byte was used per bucket to store whether the bucket is possibly empty or not. This CL changes this such that each bucket only needs a single bit. PossiblyEmptyBuckets is now a word in the page header. If more bits are needed than fit into a single word, an external bitmap is allocated using AlignedAlloc. Storing this on the page header, allows to remove initial_buckets from the SlotSet. The SlotSet allocation is then again a power-of-2 in release mode. Reland of https://crrev.com/c/1906376: Incorrect DCHECK was removed. WordsForBuckets was simplified and a test was added for it. Bug: chromium:1023139 Change-Id: I9a08e03a9c10e5781a146b9a28dab38824aad91f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1954391Reviewed-by:
-
Clemens Backes authored
This removes the --experimental-wasm-sat-f2i-conversions flag. This feature is shipped since v7.5. R=ahaas@chromium.org Change-Id: I354d9528be40caac77cd4e41adcd39d013448339 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958009Reviewed-by:
-
Michael Achenbach authored
Some fuzz test cases set Math.min to a different function. Let the fake typed array constructors remember the original Math.min. No-Try: true Bug: chromium:1024815 Change-Id: Ia389439fe6757f2497e22187042c5cdf1d1c649f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958050 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#65383}
-
Ng Zhi An authored
Mostly for f32x4 instructions. Bug: v8:9561 Change-Id: I3a3dc06305acb9e336c494fc399cf5d21518c0e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1950488Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#65382}
-
Clemens Backes authored
This caused compile errors since https://crrev.com/c/1934407: ld.lld: error: undefined symbol: v8::debug::AccessorPair::CheckCast(v8::Value*) >>> referenced by debug-interface.h:578 (../../src/debug/debug-interface.h:578) >>> obj/test/cctest/cctest_sources/test-debug.o:(TestGetPrivateMethodsAndAccessors()) R=verwaest@chromium.org CC=joyee@igalia.com Change-Id: I4a727ddd2673c75ec16368459114cfcafdd18912 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955595 Auto-Submit: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Joyee Cheung <joyee@igalia.com> Reviewed-by:
-
Simon Zünd authored
This CL is a prepatory step towards moving the stack locals blacklist from the DebugEvaluateContext to the respective {ScopeInfo} objects. The locals blacklist is used during local debug evaluate to decide whether a context lookup can advance the context chain upwards, or if lookup needs to stop at the current scope. This CL also introduces a "Recreate" static helper method, that allows an existing ScopeInfo to be cloned, but with a locals blacklist attached. This will be needed since blacklists are only created on-demand during debugging. R=leszeks@chromium.org Bug: chromium:1027475, v8:9938 Change-Id: I673dbc99ce9fdc84cb5cda3f9710ba2b76ab92ee Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1946349 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: -
Simon Zünd authored
R=yangguo@chromium.org Change-Id: Ia58394ec14b34dcd9641d6cf3a810ac272431801 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1958006 Commit-Queue: Simon Zünd <szuend@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Auto-Submit: Simon Zünd <szuend@chromium.org> Reviewed-by:
-
Clemens Backes authored
For each wasm feature flag, this adds a link to the proposal repository, and states who is the v8-side owner of the implementation. For stated and shipped features, it also sais since which v8 version this is the case. It also adds some documentation about the meaning of the three categories (experimental, stages, shipped). R=mstarzinger@chromium.org, adamk@chromium.org No-Try: true Change-Id: Idbb26eb9e68c7a81aed0e1c1b1d12d5de40d7c2e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1954395 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#65378}
-
Zhang, Shiyu authored
This is a reland of 5253d7bf Original change's description: > [runtime] Cache prototype chain enumerable keys in PrototypeInfo > > This CL adds a prototype_chain_enum_cache to cache the enumeration of a > prototype and its entire chain on the PrototypeInfo. It can improve for-in > performance via simply merging the receiver enumeration with this cache. > > It improves the score of JetStream2-tagcloud-SP case by ~9% on IA Chromebook. > > Contributed by tao.pan@intel.com > > Change-Id: Ib40bfe41e772672337155584672f06fa1ba1e70d > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1870844 > Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Cr-Commit-Position: refs/heads/master@{#65224} Change-Id: I93b74727c46abbaab163324c50fbd977fcc9bb36 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955232Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/51a024f..c3cb105 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I8a81064241961d90f3d9c4dce490a90d060eeb49 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955990Reviewed-by:
-
- 07 Dec, 2019 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/35a759a..4f02786 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/447ab8a..51a024f Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/fe18a43..6b52dc2 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/d1940b1..57e481c Rolling v8/tools/luci-go: git_revision:7d11fd9e66407c49cb6c8546a2ae45ea993a240c..git_revision:37a855b64d59b7f079c9a0e5368f2757099d14d3 Rolling v8/tools/luci-go: git_revision:7d11fd9e66407c49cb6c8546a2ae45ea993a240c..git_revision:37a855b64d59b7f079c9a0e5368f2757099d14d3 Rolling v8/tools/luci-go: git_revision:7d11fd9e66407c49cb6c8546a2ae45ea993a240c..git_revision:37a855b64d59b7f079c9a0e5368f2757099d14d3 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: Ie906df3d577d1b5de1e520d2ac9b1a50d08c68dd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955988Reviewed-by:
-
- 06 Dec, 2019 11 commits
-
-
Anton Bikineev authored
This fixes DCHECK build with --noincremental-marking flag. Change-Id: If1e8f9ec09bd91e628c3e92bbcd40f6960473f5b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955598Reviewed-by:
-
David Carlier authored
This check is useful for preventing a segfault upon usage of this argument. Change-Id: I3cc77f84d7e3ca2a96ec36a50bddb9c2eadeb62f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1946336Reviewed-by:
-
Ross McIlroy authored
Change-Id: I9be7c10193553088b72b6303408636b4fea64f5c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955594Reviewed-by:
Dan Elphick <delphick@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Auto-Submit: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#65372}
-
Seth Brenith authored
This change is the first part of adding Torque support for a "bitfield struct", which represents a set of bitfields packed together into an integer value. With this change, Torque can generate the list of BitField template specializations that allow runtime code to use the bitfield values. The flags used in SharedFunctionInfo are converted to Torque to exercise this functionality. Bitfield values are not yet accessible directly from Torque code. Bug: v8:7793 Change-Id: I9e4a3df7c847111b6e02e513f175dbf938b0be35 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1949047 Commit-Queue: Seth Brenith <seth.brenith@microsoft.com> Reviewed-by:
-
Clemens Backes authored
This adds a method to generate the debug side table via Liftoff, and adds first tests that check that the number of entries is as expected. These tests will be extended in a follow-up CL to test the actual content of the debug side table. R=mstarzinger@chromium.org Bug: v8:10019 Change-Id: I393ffabed3408463ffba232a66e2dffd7dd74f15 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1954390 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
-
Dan Elphick authored
Add --benchmark option to allow selecting a benchmark other v8.browsing_desktop. If not using the default, the options to generate v8 runtime call stats will be automatically added. Adds --stdev option to calculate the standard deviation of the results in the table. Add --device and --browser option that are passed through to run_benchmark. Change-Id: I8c57c9eba7aea84108a2e3d4fdd098a7695cad53 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955588Reviewed-by:
Mythri Alle <mythria@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#65369}
-
Joshua Litt authored
Bug: v8:9838 Change-Id: Ib2741501330629a29c1f3fe4f4a93a73982ab4de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1929400 Commit-Queue: Joshua Litt <joshualitt@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#65368}
-
Anna Henningsen authored
The recently introduced usage of `std::logical_and` requires this. This un-breaks building Node.js with the current V8 master branch on FreeBSD. Refs: https://chromium-review.googlesource.com/c/v8/v8/+/1940476 Refs: https://github.com/nodejs/node-v8/issues/124 Change-Id: Ic9d63c40e1b533f7f1c59a05f8577ee0bb0d6aa1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955584Reviewed-by:
-
Igor Sheludko authored
... broken during porting to Torque here https://chromium-review.googlesource.com/c/v8/v8/+/1891610 Bug: chromium:1028538 Bug: v8:8906 Bug: v8:4153 Change-Id: I0fb33299832964a1990e9e60a351aa88e246b3a3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955585 Commit-Queue: Igor Sheludko <ishell@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Auto-Submit: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Deepti Gandluri authored
Change-Id: I607e9565e29b2159c1783cd58fb5a2e19c02b221 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1955524 Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by:
-
Clemens Backes authored
Sign extension opcodes are already tested in the interpreter since https://crrev.com/c/1083337, thus remove the obsolete TODO. R=gdeepti@chromium.org No-Try: true Change-Id: I08323b9d43fa46d1fcf9965e5106a68767f695b5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1954400 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:
-
