- 13 Jul, 2017 20 commits
-
-
Michael Starzinger authored
R=bmeurer@chromium.org BUG=v8:6408 Change-Id: I34abbcdc2fc47df44938bac0e59f9982c935c657 Reviewed-on: https://chromium-review.googlesource.com/569963Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#46631}
-
Clemens Hammacher authored
This reverts commit 5648aad5. Reason for revert: Compile error on mips: https://build.chromium.org/p/client.v8.ports/builders/V8%20Mips%20-%20builder/builds/10732 Original change's description: > [wasm] Don't store global handles in the interpreter > > Storing global handles in the interpreter is dangerous, because the > global handles are strong roots into the heap. The interpreter itself is > referenced from the heap via a Managed. Hence the interpreter keeps the > instance alive, while the instance keeps the Managed alive. So the GC > will never collect them. > > This CL refactors this to only store the handle to the instance object > while executing in the interpreter, and clearing it when returning. > It also removes the cache of import wrappers, as it should not be > performance critical, but keeps lots of objects alive. If it turns out > to be performance critical, we will have to reintroduce such a cache > stored in the WasmDebugInfo object. > > R=titzer@chromium.org > CC=ahaas@chromium.org > > Bug: chromium:610330 > Change-Id: I54b489dadc16685887c0c1a98da6fd0df5ad7cbb > Reviewed-on: https://chromium-review.googlesource.com/567058 > Reviewed-by: Ben Titzer <titzer@chromium.org> > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#46629} TBR=titzer@chromium.org,clemensh@chromium.org Change-Id: Ifadfb885f937f37bb3eab4732a97f20ff40c2583 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:610330 Reviewed-on: https://chromium-review.googlesource.com/569962Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#46630}
-
Clemens Hammacher authored
Storing global handles in the interpreter is dangerous, because the global handles are strong roots into the heap. The interpreter itself is referenced from the heap via a Managed. Hence the interpreter keeps the instance alive, while the instance keeps the Managed alive. So the GC will never collect them. This CL refactors this to only store the handle to the instance object while executing in the interpreter, and clearing it when returning. It also removes the cache of import wrappers, as it should not be performance critical, but keeps lots of objects alive. If it turns out to be performance critical, we will have to reintroduce such a cache stored in the WasmDebugInfo object. R=titzer@chromium.org CC=ahaas@chromium.org Bug: chromium:610330 Change-Id: I54b489dadc16685887c0c1a98da6fd0df5ad7cbb Reviewed-on: https://chromium-review.googlesource.com/567058Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#46629}
-
Pierre Langlois authored
When disassembling some instructions we would print `r12`, which can be confusing when the rest of the disassembly consistently uses `ip`. Bug: Change-Id: Id4cfc5805ef102a0845cdaaa8390e618ee981b19 Reviewed-on: https://chromium-review.googlesource.com/570038Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Pierre Langlois <pierre.langlois@arm.com> Cr-Commit-Position: refs/heads/master@{#46628}
-
Clemens Hammacher authored
There is just one version now, called IsPowerOfTwo. It accepts any integral type. There is one slight semantical change: Called with kMinInt, it previously returned true, because the argument was implicitly casted to an unsigned. It's now (correctly) returning false, so I had to add special handlings of kMinInt in machine-operator-reducer before calling IsPowerOfTwo on that value. R=mlippautz@chromium.org,mstarzinger@chromium.org,jgruber@chromium.org,ishell@chromium.org,yangguo@chromium.org Change-Id: Idc112a89034cdc8c03365b778b33b1c29fefb38d Reviewed-on: https://chromium-review.googlesource.com/568140Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#46627}
-
Clemens Hammacher authored
This CL changes the USE macro to accept more than one parameter. This is particularly interesting for calling a method on each type in a parameter pack, as in: template<typename... T> void foo(T&&... ts) { USE(do_something(ts)...); } Drive-by fix: Allow to pass arbitrary types to USE, including references. This might prevent a copy for pass-by-value. R=ishell@chromium.org, tebbi@chromium.org Also-by: tebbi@chromium.org Change-Id: I544e83bb996aaa638e7512295973dd3e742254bc Reviewed-on: https://chromium-review.googlesource.com/567507Reviewed-by:Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#46626}
-
Yang Guo authored
This is for backwards ABI compatibility to version 6.0. R=bmeurer@chromium.org Bug: v8:6592 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I20f3fa79324511c6e393ddaad50880f22ef6df77 Reviewed-on: https://chromium-review.googlesource.com/569758Reviewed-by:
-
Clemens Hammacher authored
It's ok that the instance of the called code object is different from the caller instance. This happens if one instance calls an exported function of another instance. R=ahaas@chromium.org Bug: chromium:739768 Change-Id: I6afa8332a9b33fe32e9332cdca573053f058421d Reviewed-on: https://chromium-review.googlesource.com/568494Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#46624}
-
Clemens Hammacher authored
It used to be module-relative, but since we switched to decoding sections individually, the offsets would be section-relative. This CL fixes this by adding the buffer offset to the reported locations. R=ahaas@chromium.org Change-Id: I27240832e5cbd625d6b952678503252017dd83f3 Reviewed-on: https://chromium-review.googlesource.com/568488 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
-
Igor Sheludko authored
The shortcuts ensure that field type generalization is properly propagated in the transition graph. Bug: chromium:738763 Change-Id: Id701a6f95ed6ea093c707fbe0bac228f1f856e9f Reviewed-on: https://chromium-review.googlesource.com/567992 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#46622}
-
Clemens Hammacher authored
The DCHECK is supposed to check that the read in the next line does not read out of bounds. Hence we have to use {pc} and not {pc_}. I accidentally triggered this while writing an unrelated test case, but now fail to reproduce. R=ahaas@chromium.org Change-Id: Ia3fa9a9874866dc14180b22b9af526459fbda495 Reviewed-on: https://chromium-review.googlesource.com/568487Reviewed-by: -
Michael Starzinger authored
This correctly types values loaded via {LoadElement} nodes from arrays of HOLEY_DOUBLE_ELEMENTS elements kind as {Type::NumberOrHole}. Even though "the hole" is still encoded as a tagged NaN, the type system still needs to consider it as a potential hole value. R=bmeurer@chromium.org TEST=mjsunit/regress/regress-crbug-736575 BUG=chromium:736575 Change-Id: Ib869284900a4affb2ddaa1d2a96df9443dba6921 Reviewed-on: https://chromium-review.googlesource.com/567180Reviewed-by: -
Andreas Haas authored
The instruction sequence consumes a significant amount of memory, so it should be deallocated as early as possible. This CL separates the zone which is used by the code generator from the zone which is used by the instruction selector. Thereby we can delete the instruction selector zone, which contains the instruction sequence, already after AssembleCode, and not only after FinalizeCode. For WebAssembly this means that the instruction sequence gets deleted on the background tasks already and does not stay alive until the main threads deletes it. R=bmeurer@chromium.org, neis@chromium.org CC=mtrofin@chromium.org Change-Id: I090a2140ca05ae3bcc66268b0eddb08846fea690 Reviewed-on: https://chromium-review.googlesource.com/566831 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
Mircea Trofin <mtrofin@chromium.org> Reviewed-by:
-
Mike Stanton authored
Bug: v8:1956 Change-Id: I41af0cf5eb2fbb9f1d9d4172f3f546bcc2a715dc Reviewed-on: https://chromium-review.googlesource.com/548639 Commit-Queue: Michael Stanton <mvstanton@chromium.org> Reviewed-by:
Daniel Clifford <danno@chromium.org> Cr-Commit-Position: refs/heads/master@{#46618}
-
Georg Neis authored
Enabling background code assembly broke --code-comments. This CL "fixes" it for now by simply skipping the printing of inlining stack info. R=bmeurer@chromium.org Bug: v8:6048 Change-Id: I8b9ea629c7c302198484510a7234014bfbfd890b Reviewed-on: https://chromium-review.googlesource.com/569163Reviewed-by:
-
Michael Achenbach authored
This reverts commit 0d910860. Reason for revert: Bot is fixed again. Original change's description: > [CQ] Temporarily exclude broken bot from CQ > > TBR=neis@chromium.org > > Change-Id: I59903a40c1ca47cce3e5744c51a2abda93e45dad > Reviewed-on: https://chromium-review.googlesource.com/567931 > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#46580} TBR=machenbach@chromium.org,neis@chromium.org Bug: chromium:741505 Change-Id: I47068e6364e8b417b75ffd687e7758c41fc0ed0f No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/569738Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#46616}
-
Peter Marshall authored
Previously we enforced that all lengths for ArrayLike objects must be within Smi range, but all negative numbers should actually be first converted to +0. Bug: chromium:740372 Change-Id: If50de9ce0eeb7cb09e14b8e8803f434350d00508 Reviewed-on: https://chromium-review.googlesource.com/566867Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#46615}
-
Ben Noordhuis authored
Insertion into a collection changes the map because of the addition of the hash value property. Check the root map, not the current map. Fixes: https://github.com/nodejs/node/issues/14139 Change-Id: Iabcea5337323b9b6deffa1a06892c1cb749f2065 Reviewed-on: https://chromium-review.googlesource.com/566833Reviewed-by:
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/7e59b44..f64cb20 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/buildtools/+log/1dcd1bd..c2827ae Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/08d8c9f..1286055 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/4dc63de..f6f6b65 TBR=machenbach@chromium.org,hablich@chromium.org Change-Id: I98b37d30910e31eed44072520b817ebec95c0f98 Reviewed-on: https://chromium-review.googlesource.com/569407Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#46613}
-
agrieve authored
BUG=chromium:738469 Review-Url: https://codereview.chromium.org/2962213002 Cr-Commit-Position: refs/heads/master@{#46612}
-
- 12 Jul, 2017 20 commits
-
-
Sathya Gunasekaran authored
Bug: chromium:740694 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Ib23bca1942c25d8a9f32e12be3f7b50fc3ab55c8 Reviewed-on: https://chromium-review.googlesource.com/568222 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#46611}
-
Adam Klein authored
Change-Id: I0f4756efdaa9468bcbd88949ddb2e2d7cae3ce06 Reviewed-on: https://chromium-review.googlesource.com/568917Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#46610}
-
Adam Klein authored
Change-Id: Id46a9007021c8f1508a9a737b1e35d12bffd872b Reviewed-on: https://chromium-review.googlesource.com/568254Reviewed-by:
-
Ross McIlroy authored
Didn't seem to help and caused a couple of regressions. BUG=v8:6243,chromium:740124 Change-Id: I72887ba245a524211dbf181c77d0cdc6d917d090 Reviewed-on: https://chromium-review.googlesource.com/568480 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#46608}
-
Adam Klein authored
When we abort preparsing, we have to reset the Scope state, to ensure re-parsing will leave us in the proper Zone. Resetting of rare_data_ was missing, causing this to fail in some cases. Bug: chromium:740803 Change-Id: I7ce70f9c4670eaf1b76745ae8231eb95625b0f4b Reviewed-on: https://chromium-review.googlesource.com/568784Reviewed-by:
Caitlin Potter <caitp@igalia.com> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#46607}
-
Adam Klein authored
It's been regularly timing out on the Linux debug bot. TBR=machenbach@chromium.org Change-Id: I250fc55acb5d714c7060edb691eb9759a7d38a15 Reviewed-on: https://chromium-review.googlesource.com/568794Reviewed-by:
-
Karl Schimpf authored
This turns on collection of function size bytes, and decode time for functions in all cases (both background and foreground). Bug: v8:6361 Change-Id: I5d982ec4452596210b3ea9858126820ad0c3eacf Reviewed-on: https://chromium-review.googlesource.com/568781 Commit-Queue: Karl Schimpf <kschimpf@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#46605}
-
Jaideep Bajwa authored
Follow up on https://codereview.chromium.org/2740353002. Created PosixDefaultTimezoneCache which is a subclass of PosixTimezoneCache containing definition of LocalTimezone and LocalTimeOffset which is separate for different OS. R=littledan@chromium.org, ulan@chromium.org BUG=v8:6578 LOG=N Change-Id: I58342893aeefe79ac50e1df041d614fc473f15bf Reviewed-on: https://chromium-review.googlesource.com/568686Reviewed-by:
Daniel Ehrenberg <littledan@chromium.org> Commit-Queue: Jaideep Bajwa <bjaideep@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#46604}
-
Camillo Bruni authored
By creating the boilerplate only on the second instantiation we cannot propagate back the elements transitions early enough. The resulting literals would change the initial ElementsKind one step too late and already pollute ICs that went to monomorphic state. - Disable lazy AllocationSites for literals containing arrays - Introduce new ComplexLiteral class to share code between ObjectLiteral and ArrayLiteral - RegexpLiteral now no longer needs a depth_ field Bug: v8:6517, v8:6519, v8:6211 Change-Id: Ia88d1878954e8895c3d00a7dda8d71e95bba005c Reviewed-on: https://chromium-review.googlesource.com/563305Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
-
Camillo Bruni authored
This is a reland of f720d024 Original change's description: > [mjsunit] Improve mjsunit stracktrace readability > > Format the function name and file-position into proper columns to easily spot > where the test code ends and the mjsunit framework code starts. > > BEFORE: > Stack: Error > at new MjsUnitAssertionError (test/mjsunit/mjsunit.js:36:18) > at failWithMessage (test/mjsunit/mjsunit.js:310:11) > at fail (test/mjsunit/mjsunit.js:327:12) > at assertEquals (test/mjsunit/mjsunit.js:398:7) > at closure (test/mjsunit/regress/regress-4121.js:20:7) > at literals_sharing_test (test/mjsunit/regress/regress-4121.js:27:3) > at test (test/mjsunit/regress/regress-4121.js:37:5) > at eval (eval at <anonymous> (test/mjsunit/regress/regress-4121.js:49:6), <anonymous>:1:1) > at test/mjsunit/regress/regress-4121.js:49:6 > at Array.forEach.call (test/mjsunit/regress/regress-4121.js:50:7) > throw new MjsUnitAssertionError(message); > > AFTER: > Stack: MjsUnitAssertionError > at assertEquals test/mjsunit/mjsunit.js 398:7 > at closure test/mjsunit/regress/regress-4121.js 20:7 > at literals_sharing_test test/mjsunit/regress/regress-4121.js 27:3 > at test test/mjsunit/regress/regress-4121.js 37:5 > at eval eval at <anonymous> (test/mjsunit/regress/regress-4121.js:49:6) > at test/mjsunit/regress/regress-4121.js 49:6 > at Array.forEach.call test/mjsunit/regress/regress-4121.js 50:7 > throw new MjsUnitAssertionError(message); > > > Change-Id: Iad3460a648e26effb43c00426ab043743ee6a138 > Reviewed-on: https://chromium-review.googlesource.com/563627 > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Commit-Queue: Camillo Bruni <cbruni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#46589} Change-Id: I44bf07f7be4114369315605542cafd17345b4397 Reviewed-on: https://chromium-review.googlesource.com/567063Reviewed-by:
-
Adam Klein authored
JSFunction::SetName can fail if it tries to create a string with length > String::kMaxLength (either by prepending "set "/"get " or by surrounding a Symbol descriptor with "["/"]"). This patch propagates that exception to the surrounding code rather than CHECK-failing. Bug: chromium:740398 Change-Id: I394943af481f3147387dd82ec5862d7071d57827 Reviewed-on: https://chromium-review.googlesource.com/566092Reviewed-by:
-
Alexandre Talon authored
The JSTypedLowering reducer was returning Changed(node) when it did not change the node, in case the node was a speculative number comparison node. Bug: Change-Id: I2082e4c2e45078b343e427f54d61d4e0a323a64f Reviewed-on: https://chromium-review.googlesource.com/568036Reviewed-by:
-
Clemens Hammacher authored
The problem popped up when passing the constants by reference (https://chromium-review.googlesource.com/c/565141). It's a bit ugly, but, the C++11 standard requires a definition additionally to the existing declaration in the body of the class: 9.4.2/4: If a static data member is of const literal type, its declaration in the class definition can specify a brace-or-equal-initializer in which every initializer-clause that is an assignment-expression is a constant expression. A static data member of literal type can be declared in the class definition with the constexpr specifier; if so, its declaration shall specify a brace-or-equal-initializer in which every initializer-clause that i an assignment-expression is a constant expression. [Note: In both these cases, the member may appear in constant expressions. — end note] The member shall still be defined in a namespace scope if it is odr-used (3.2) in the program and the namespace scope definition shall not contain an initializer. Drive-by: Make the static constants constexpr. R=bmeurer@chromium.org Change-Id: Idc3d20bf2adf31d874c23ff8bfec52437789160a Reviewed-on: https://chromium-review.googlesource.com/567506Reviewed-by:
-
Mythri authored
In branch elimination phase, control paths are updated when visiting the nodes. We first create a control path and then check if it is same as the exisiting one. If it is the same we discard the newly created one. Since these are created in the zone memory the memory will not be released till the entire pass is over. This cl changes it to first check if the control path has changed and create a new path only if it has changed. Bug: chromium:725664,v8:6150 Change-Id: I67fbea13036f85999c7ed366c571f8dc1c17a023 Reviewed-on: https://chromium-review.googlesource.com/563406Reviewed-by:
-
Ulan Degenbaev authored
BUG=chromium:694255 Change-Id: I49618ccb7e7c87dfd8ba8b2359c4384198fd1c30 Reviewed-on: https://chromium-review.googlesource.com/568306 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Daniel Clifford authored
This makes it possible for automated tests to distinguish between CHECK failures and DCHECK failures, the latter of which will continue to run in release builds after the assertion failure point. Change-Id: Ie26978c0342d401a8c85f3261749739195087579 Reviewed-on: https://chromium-review.googlesource.com/565515 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Reviewed-by:
-
Michael Starzinger authored
This makes sure we leave some gap on the stack whenever compilation jobs are being finalized. Such a finalization can trigger assembling back on the main thread, hence requiring a non-negligible amount of stack. This is in sync with other {Runtime_CompileFoo} methods. R=ishell@chromium.org BUG=chromium:740400,chromium:741599 Change-Id: I96fbd524c3cd443a1f5a8e22925b92407fadfb63 Reviewed-on: https://chromium-review.googlesource.com/568142Reviewed-by: -
Camillo Bruni authored
- Update InitializeAllocationMemento to use newer CSA helper - Fix AllocateJSArray to create AllocationMementos for empty arrays as well Bug: v8:6211 Change-Id: I8731b04cdd500b877a54dee67f00f2899d91d86d Reviewed-on: https://chromium-review.googlesource.com/566810 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Georg Neis authored
R=ahaas@chromium.org, bmeurer@chromium.org Bug: v8:6048 Change-Id: I5641cb1036fb0c6bf0803de3df9ddeb5787a93de Reviewed-on: https://chromium-review.googlesource.com/563308Reviewed-by:
-
Georg Neis authored
This reverts commit f720d024. Reason for revert: Bot failure at https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20-%20custom%20snapshot%20-%20debug/builds/15690 Original change's description: > [mjsunit] Improve mjsunit stracktrace readability > > Format the function name and file-position into proper columns to easily spot > where the test code ends and the mjsunit framework code starts. > > BEFORE: > Stack: Error > at new MjsUnitAssertionError (test/mjsunit/mjsunit.js:36:18) > at failWithMessage (test/mjsunit/mjsunit.js:310:11) > at fail (test/mjsunit/mjsunit.js:327:12) > at assertEquals (test/mjsunit/mjsunit.js:398:7) > at closure (test/mjsunit/regress/regress-4121.js:20:7) > at literals_sharing_test (test/mjsunit/regress/regress-4121.js:27:3) > at test (test/mjsunit/regress/regress-4121.js:37:5) > at eval (eval at <anonymous> (test/mjsunit/regress/regress-4121.js:49:6), <anonymous>:1:1) > at test/mjsunit/regress/regress-4121.js:49:6 > at Array.forEach.call (test/mjsunit/regress/regress-4121.js:50:7) > throw new MjsUnitAssertionError(message); > > AFTER: > Stack: MjsUnitAssertionError > at assertEquals test/mjsunit/mjsunit.js 398:7 > at closure test/mjsunit/regress/regress-4121.js 20:7 > at literals_sharing_test test/mjsunit/regress/regress-4121.js 27:3 > at test test/mjsunit/regress/regress-4121.js 37:5 > at eval eval at <anonymous> (test/mjsunit/regress/regress-4121.js:49:6) > at test/mjsunit/regress/regress-4121.js 49:6 > at Array.forEach.call test/mjsunit/regress/regress-4121.js 50:7 > throw new MjsUnitAssertionError(message); > > > Change-Id: Iad3460a648e26effb43c00426ab043743ee6a138 > Reviewed-on: https://chromium-review.googlesource.com/563627 > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Commit-Queue: Camillo Bruni <cbruni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#46589} TBR=machenbach@chromium.org,cbruni@chromium.org,ishell@chromium.org Change-Id: I631cec7f318637ce2f60500e2bf0ab7fe1f6d09e No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/567062Reviewed-by:
-
