- 22 Nov, 2018 8 commits
-
-
peterwmwong authored
Initial port of Array.p.join came before Torque had exception handling. This small cleanup also simplifies a future CL porting TypedArray.p.join. Bug: v8:7624 Change-Id: I74f3880ee6e87917bc87e41d94be1a83b039384b Reviewed-on: https://chromium-review.googlesource.com/c/1347514Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Peter Wong <peter.wm.wong@gmail.com> Cr-Commit-Position: refs/heads/master@{#57712}
-
Yang Guo authored
This reverts commit 1d726111. Reason for revert: This breaks a layout test, and blocks V8 roll https://ci.chromium.org/p/chromium/builders/luci.chromium.try/win7_chromium_rel_ng/135831 Original change's description: > Implement Faster MicrotaskQueue Step 2 > > This is an implementation of https://bit.ly/v8-faster-microtask-queues > step 2. > > This CL overhauls MicrotaskQueue class, the previous one is on V8 heap, > and the new one is on C++ heap. > > Benchmark: > This CL improves a benchmark score around promise by 5~23%. > https://github.com/v8/promise-performance-tests > https://docs.google.com/spreadsheets/d/1HtwZGzUAGJYg87VmYhV9hLdvfddlCtC6Oz0iOj-WwQA/edit#gid=1952666737 > > Bug: chromium:887920, v8:7253 > Change-Id: I1f26e02c45ae60ae39d1ccc168daa98bca4663d9 > Reviewed-on: https://chromium-review.googlesource.com/c/1290751 > Commit-Queue: Taiju Tsuiki <tzik@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Reviewed-by: Adam Klein <adamk@chromium.org> > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57681} TBR=ulan@chromium.org,adamk@chromium.org,yangguo@chromium.org,ishell@chromium.org,bmeurer@chromium.org,tzik@chromium.org Change-Id: I639882a95fe63c029a2e53d610dc4133d1ac48f2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:887920, v8:7253 Reviewed-on: https://chromium-review.googlesource.com/c/1347473 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#57711}
-
Michael Achenbach authored
This commit adds a --run-skipped flag to the test runner that will bypass the 'SKIP' status. Bug: v8:8485 Change-Id: Iac012bdaf2de6b0f8e44ed3a65bc9330709527bb Reviewed-on: https://chromium-review.googlesource.com/c/1346490 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#57710}
-
Jaroslav Sevcik authored
Bug: v8:8361 Change-Id: If5d7e8dd6c4e800ce6f8b82d197c29111bc8707d Reviewed-on: https://chromium-review.googlesource.com/c/1340296Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#57709}
-
Tao Pan authored
IA support both "push reg" and "push [mem]" assemble instruction. Use OperandGenerator::UseAny() for initializing Operand of kX64Push with should be more willing to use spill slots (Use constraints are marked as register-beneficial; UseAny are not) UnallocatedOperand: :REGISTER_OR_SLOT. That way, the register allocator Change-Id: I8ffd66915c8acd64221182710257232ef19f06d6 Reviewed-on: https://chromium-review.googlesource.com/c/1337312Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#57708}
-
Jaroslav Sevcik authored
With constant field tracking, we get more properties on instance. This negatively affects the common scenario where objects are used as module, i.e., they have large number of constant functions as properties. In that case, we would transition the objects to dictionary mode. Bug: v8:8361 Change-Id: If4831bd081f3c45be651e051e7375eb275d265b4 Reviewed-on: https://chromium-review.googlesource.com/c/1344110 Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#57707}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/a2bfd53..05ea63b Rolling v8/buildtools: https://chromium.googlesource.com/chromium/buildtools/+log/da9b294..04161ec Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/d115075..aa21a92 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/e47ac15..d66dad7 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/aa6b9c8..7fa2bdf Rolling v8/tools/luci-go:infra/tools/luci/isolate/${platform}: https://chrome-infra-packages.appspot.com/infra/tools/luci/isolate/${platform}/+log/git_rev..git_rev TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I5c181380da2230f62677f345c6584f3fd856b75f Reviewed-on: https://chromium-review.googlesource.com/c/1347890 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#57706}
-
Shiyu Zhang authored
This is a reland of 6ec90ece Original change's description: > Reland "Create a fast path to get migration target when updating map" > > This is a reland of c285380c > > Original change's description: > > Create a fast path to get migration target when updating map > > > > During map updating, store the pointer to new map in the > > raw_transitions slot of the old map that is deprecated from map > > transition tree. Thus, we can get the migration target directly > > instead of TryReplayPropertyTransitions when updating map. > > > > This can improve Speedometer2.0 Elm-TodoMVC case by ~5% on ATOM > > Chromebook and ~9% on big-core Ubuntu. > > > > Change-Id: I56f9ce5183bbdd567b964890f623ef0ceed9b7db > > Reviewed-on: https://chromium-review.googlesource.com/1233433 > > Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> > > Reviewed-by: Igor Sheludko <ishell@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#56303} > > Change-Id: Idf0b7716b92a6a15bfe58721c2c34dbd02b31137 > Reviewed-on: https://chromium-review.googlesource.com/c/1270261 > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> > Cr-Commit-Position: refs/heads/master@{#56588} Change-Id: Iad23455f66c83340430370be6670bac493c638a1 Reviewed-on: https://chromium-review.googlesource.com/c/1309305 Commit-Queue: Shiyu Zhang <shiyu.zhang@intel.com> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#57705}
-
- 21 Nov, 2018 32 commits
-
-
Ross McIlroy authored
Moves allocation of the WasmModuleObject for asm.js code out of SyncCompileTranslatedAsmJS since that is called when we are compiling the native context independent SharedFunctionInfo and the WasmModuleObject requires a native context. Instead save the members required to create the object in the AsmWasmData and create it during module instantiation. Note: since the Wasm module is an implementation detail for asm_wasm code and isn't exposed, this doeesn't have semantic change for asm.js code. As part of this change, the AsmWasmData is changed from a FixedArray to a dedicated struct. Some logic is also moved from module-compiler to wasm-engine to make the seperation between Wasm SyncCompile and AsmJS SyncCompile more clear. BUG=chromium:900535,v8:8395 Change-Id: Ia48469c095b0688f210aa86e7430c9ab4ea4b26b Reviewed-on: https://chromium-review.googlesource.com/c/1345509 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#57704}
-
Erik Luo authored
Types such as "function" have a ValueMirror that does not override "buildObjectPreview()". This CL updates clients to check that the preview was actually built after call it. Bug: chromium:907400 Change-Id: Id569c98363d47b259a40790b596efedb3d14abc2 Reviewed-on: https://chromium-review.googlesource.com/c/1347067Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Erik Luo <luoe@chromium.org> Cr-Commit-Position: refs/heads/master@{#57703}
-
Jakob Kummerow authored
In preparation for incrementally migrating subclasses to deriving from FixedArrayPtr/FixedArrayBasePtr. Once that is done for all subclasses, this duplication will be dropped again. Bug: v8:3770 Change-Id: I6d664997fdcb18f7c0f37183d9f920ae30f3b749 Reviewed-on: https://chromium-review.googlesource.com/c/1345325Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#57702}
-
Sigurd Schneider authored
We haven't put 64bit constants in the constant pool for a while. This CL removes the support, simplifying the implementation. Change-Id: I2c8972ea74dc71ccd5c9d333947d681dad2ea6c0 Bug: v8:8054 Reviewed-on: https://chromium-review.googlesource.com/c/1346109 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#57701}
-
Junliang Yan authored
Sharing WasmCall/StubCall will lead to relocation being processed more than once in NativeModule::AddCode for wasm. R=joransiu@ca.ibm.com Change-Id: I88d9a1a956fe36ef81e0a4c61d7dedf868bdf9a3 Reviewed-on: https://chromium-review.googlesource.com/c/1344510 Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Reviewed-by: Joran Siu <joransiu@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#57700}
-
Toon Verwaest authored
Change-Id: I50320af8484f247656b79beb3195f371635f6797 Reviewed-on: https://chromium-review.googlesource.com/c/1346495Reviewed-by: Igor Sheludko <ishell@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#57699}
-
Junliang Yan authored
Port de2681c1 Original Commit Message: This adds a {PrintRegister} method which prints the given register in a readable way (e.g. "eax", ... on ia32). This is currently only used in Liftoff. The {RegisterConfiguration} class has the same functionality, and I plan to make {RegisterConfiguration} also use the new {RegisterName} functions in a follow-up CL. R=clemensh@chromium.org, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I8359ed22ebe88d5c30a45a9c6f3caa3b03d902ee Reviewed-on: https://chromium-review.googlesource.com/c/1344509 Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Reviewed-by: Joran Siu <joransiu@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#57698}
-
Hannes Payer authored
Bug: chromium:852420 Change-Id: I01d0bed33a573adbe1d9365868d63ea9c3cb0552 Reviewed-on: https://chromium-review.googlesource.com/c/1346499Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#57697}
-
Toon Verwaest authored
It's unclear that this helps performance. Let's see what the bots say. Change-Id: Ic28783c90495f6ce01b4980d84794d394f941a4f Reviewed-on: https://chromium-review.googlesource.com/c/1346331 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#57696}
-
Tobias Tebbi authored
This reverts commit d8c471ff. Reason for revert: breaks waterfall Original change's description: > [torque] change formatter to emit LF newlines on Windows > > Otherwise, it will always replace LF with CRLF, which is not what you > want if you follow the Chromium instructions for Windows, that is, > configure git with core.autocrlf = false. > > Change-Id: I30fcfc471cde79d5c80d05ce582a8507cf5810b5 > Reviewed-on: https://chromium-review.googlesource.com/c/1345150 > Reviewed-by: Daniel Clifford <danno@chromium.org> > Commit-Queue: Tobias Tebbi <tebbi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57691} TBR=danno@chromium.org,tebbi@chromium.org Change-Id: Ib30ae0d5b1803dbe8e6e8a0928cc41a6ce2d2bb8 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/1346502Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#57695}
-
Daniel Clifford authored
This reverts commit 74a0ad7d. Reason for revert: Presubmit tests fail Original change's description: > [torque] Implement intrinsics support > > Also add the first intrinsic and usage of it: %RawCast > > Bug: v8:7793 > Change-Id: Id1e3288e8bab6adb510731076a39590e8fd156be > Reviewed-on: https://chromium-review.googlesource.com/c/1344152 > Commit-Queue: Daniel Clifford <danno@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57692} TBR=danno@chromium.org,tebbi@chromium.org Change-Id: Ief78187f2edaf80c715dea676cbd40edd747ad21 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7793 Reviewed-on: https://chromium-review.googlesource.com/c/1346500Reviewed-by: Daniel Clifford <danno@chromium.org> Commit-Queue: Daniel Clifford <danno@chromium.org> Cr-Commit-Position: refs/heads/master@{#57694}
-
Igor Sheludko authored
and make the slot occupy two tagged words when pointer compression is enabled. Tbr: bmeurer@chromium.org Bug: v8:7703 Change-Id: Idcd3385cc7d5299d9bdaf6a69c7bd0591099f0bb Reviewed-on: https://chromium-review.googlesource.com/c/1346489Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#57693}
-
Daniel Clifford authored
Also add the first intrinsic and usage of it: %RawCast Bug: v8:7793 Change-Id: Id1e3288e8bab6adb510731076a39590e8fd156be Reviewed-on: https://chromium-review.googlesource.com/c/1344152 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#57692}
-
Tobias Tebbi authored
Otherwise, it will always replace LF with CRLF, which is not what you want if you follow the Chromium instructions for Windows, that is, configure git with core.autocrlf = false. Change-Id: I30fcfc471cde79d5c80d05ce582a8507cf5810b5 Reviewed-on: https://chromium-review.googlesource.com/c/1345150Reviewed-by: Daniel Clifford <danno@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#57691}
-
Sergiy Byelozyorov authored
TBR=sergiyb@chromium.org Bug: chromium:903688 Change-Id: I72b57d45286ae28c44bad0edffeb56e9142767d1 Reviewed-on: https://chromium-review.googlesource.com/c/1346494Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org> Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#57690}
-
Yang Guo authored
TBR=aseemgarg@chromium.org Change-Id: Iabb0a1d5ac065f97baf9b44815f0c5df37b426b5 Reviewed-on: https://chromium-review.googlesource.com/c/1346493Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#57689}
-
Sigurd Schneider authored
Load elimination is running together with to dead code elimination, the latter of which might eliminate allocations (in particular FinishRegion nodes). These are treated as alias nodes by load elimination, and load elimination does not immediatelly learn that a node has been disconnected. This causes load elimination to access the inputs of dead code eliminated nodes while resolving renames, which causes nullptr dereferences. This CL modifies load elimination to not resolve to a nullptr alias but simply stop before that. Change-Id: If4cef061c7c0e25f353727c9e27f790439b0beb5 Bug: chromium:906406 Reviewed-on: https://chromium-review.googlesource.com/c/1346491 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#57688}
-
Stephan Herhut authored
Adds support to render the live ranges as ascii diagram. This is similar in nature to what the c1visualizer would produce. Also, print the visualization when tracing the register allocator. Change-Id: Ib6a43f67ba356e9a80cacaddfdbd6d589c685483 Reviewed-on: https://chromium-review.googlesource.com/c/1346114Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Stephan Herhut <herhut@chromium.org> Cr-Commit-Position: refs/heads/master@{#57687}
-
Hannes Payer authored
Bug: chromium:852420 Change-Id: I54d1708991468bb062d9e7b246e724594f252e5e Reviewed-on: https://chromium-review.googlesource.com/c/1346369 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#57686}
-
Sergiy Byelozyorov authored
TBR=machenbach@chromium.org No-Try: true Bug: chromium:616879 Change-Id: I7a567060d4bbfdd5cbd8cc92a828b051ce8ddb8c Reviewed-on: https://chromium-review.googlesource.com/c/1346332 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#57685}
-
Toon Verwaest authored
This moves is_async and parenthesized_formals tracking out of the ParseAssignmentExpression header. Instead we set flags on the parser for the next arrow function: next_arrow_function_kind_ that defaults to kArrowFunction and next_arrow_formals_parenthesized_ which defaults to false. If we end up recognizing an async arrow head, we update next_arrow_function_kind_ to kAsyncArrowFunction. If we detect (...) followed by => or async(...) followed by => we set next_arrow_formals_parenthesized_ to true. When we start parsing the arrow continuation we consume the values and reset them to default for the next arrow function. Change-Id: Ia22c0068fea0f175fafc568b7339813fd10c3b5a Reviewed-on: https://chromium-review.googlesource.com/c/1345996 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#57684}
-
Toon Verwaest authored
It seems that allocating smaller pages is actually quite a bit faster than larger pages, probably because they can be cached by malloc. Let's see what the bots say. In a follow-up I'll check whether the segment-pool is actually beneficial or whether we should just remove it. This also drops SegmentSize::kLarge as a way to make compilation deterministic. Turns out that by now we need >8mb anyway, and the previous 1mb wasn't enough. At the same time the compiler was fixed to not rely on virtual addresses of zone objects anymore, and there's a bot checking whether the snapshot is determistic. Change-Id: I38cbb0d209d68b3671fd38763b42714811f4223e Reviewed-on: https://chromium-review.googlesource.com/c/1346370Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#57683}
-
Toon Verwaest authored
Use the parser's IsValidReferenceExpression as a likely-succeeding precheck. Slightly optimizes IsEvalOrArguments in the preparser and IsIdentifier for the parser (we now have FailureExpression everywhere); and replaces IsObjectLiteral||IsArrayLiteral by IsValidPattern. Change-Id: I7e9684485c0ce454e640800566eb4b0a24c6bfc8 Reviewed-on: https://chromium-review.googlesource.com/c/1345995 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#57682}
-
tzik authored
This is an implementation of https://bit.ly/v8-faster-microtask-queues step 2. This CL overhauls MicrotaskQueue class, the previous one is on V8 heap, and the new one is on C++ heap. Benchmark: This CL improves a benchmark score around promise by 5~23%. https://github.com/v8/promise-performance-tests https://docs.google.com/spreadsheets/d/1HtwZGzUAGJYg87VmYhV9hLdvfddlCtC6Oz0iOj-WwQA/edit#gid=1952666737 Bug: chromium:887920, v8:7253 Change-Id: I1f26e02c45ae60ae39d1ccc168daa98bca4663d9 Reviewed-on: https://chromium-review.googlesource.com/c/1290751 Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#57681}
-
Sergiy Byelozyorov authored
R=efoo@chromium.org, machenbach@chromium.org Bug: chromium:868202 Change-Id: I5c0860894c96a8ce14e74cb048f786908db88269 Reviewed-on: https://chromium-review.googlesource.com/c/1344150 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#57680}
-
Igor Sheludko authored
an abstraction that hides the details about how embedder data fields are encoded in EmbedderDataArrays and JSObjects. Bug: v8:7703 Change-Id: Ic9f6d9511bec557c6671aa6488b9545e353f968c Reviewed-on: https://chromium-review.googlesource.com/c/1344155 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#57679}
-
Clemens Hammacher authored
This reverts commit e8a22a70. Reason for revert: Depends on another reverted CL: https://crrev.com/c/1337585 Original change's description: > [iwyu] Add missing includes > > This fixes a presubmit error: > https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Presubmit/454 > > It also adds another missing include. > > R=machenbach@chromium.org > CC=caitp@igalia.com > > Bug: v8:7490 > Change-Id: I915a5bf431073410a67ff08471fd5e6974e31aa1 > No-Try: true > No-Tree-Checks: true > Reviewed-on: https://chromium-review.googlesource.com/c/1346111 > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57671} TBR=machenbach@chromium.org,clemensh@chromium.org Change-Id: Id01d5ff327bc50f8d21a4092ba881f5d5e982a92 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7490 Reviewed-on: https://chromium-review.googlesource.com/c/1346117Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57678}
-
Clemens Hammacher authored
This reverts commit a5336471. Reason for revert: Fails nosnap debug tests: https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Linux%20-%20nosnap%20-%20debug/21838 Original change's description: > [builtins] Implement Object.fromEntries > > Adds the Object.fromEntries() method behind > --harmony-object-from-entries. > > > Includes an initial implementation of the new experimental builtin > Object.fromEntries implemented by Daniel Clifford, and > has been modified by Caitlin Potter to support a fast case to skip > the iterator protocol when it can be done unobservably in common cases. > > There are some incidental changes: A number of CSA macros have been > updated to use TNodes, and some Context arguments have been > re-arranged to be implicit in Torque. > > > There are also a number of mjsunit tests written mirroring and > expanding on the test262 tests. > > BUG=v8:8021 > > Change-Id: I1c12bee8a2f98c6297b77d5d723910a5e3b630cc > Co-authored-by: Daniel Clifford <danno@chromium.org> > Co-authored-by: Caitlin Potter <caitp@igalia.com> > Reviewed-on: https://chromium-review.googlesource.com/c/1337585 > Commit-Queue: Daniel Clifford <danno@chromium.org> > Reviewed-by: Daniel Clifford <danno@chromium.org> > Reviewed-by: Tobias Tebbi <tebbi@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57667} TBR=danno@chromium.org,caitp@igalia.com,tebbi@chromium.org Change-Id: Id0cd8b16131f151a42dffbaca7e59ab17c68ab23 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8021 Reviewed-on: https://chromium-review.googlesource.com/c/1346116Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57677}
-
Georg Neis authored
R=jarin@chromium.org Bug: chromium:906567 Change-Id: I280569e09529457814ebc1cb8f299a80aa40a6c4 Reviewed-on: https://chromium-review.googlesource.com/c/1345992Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#57676}
-
Camillo Bruni authored
- Show spinner while parsing input - Show color boxes next transition types - Support drag-n-drop of v8.log files No-Try: true Change-Id: I360d62960e9ec05fbab388ee2ca55baf4e2c6b78 Reviewed-on: https://chromium-review.googlesource.com/c/1345151Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#57675}
-
Camillo Bruni authored
No-Try: true Change-Id: I078279bef7141c0255025efebfd3a39a57fc3bf7 Reviewed-on: https://chromium-review.googlesource.com/c/1345149Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#57674}
-
Ulan Degenbaev authored
This extracts the parts of the TypedSlotSet that are used only sequentially into a separate class called TypedSlots. The new class will be used in the concurrent marker to keep track of typed slots locally and then to merge them to the main remembered set during finalization of marking. The patch also cleans up atomics in the Iterate and ClearInvalidSlots methods that can run concurrently to each other. Bug:v8:8459 Change-Id: Id7a63041f7b99218381e5e9e1999210cab9c4369 Reviewed-on: https://chromium-review.googlesource.com/c/1340247 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Hannes Payer <hpayer@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#57673}
-