- 18 Apr, 2018 24 commits
-
-
Alexei Filippov authored
This is a reland of 9a19ce25 Original change's description: > [profiler] Ensure there's a single ProfilerListener per isolate. > > BUG=v8:7662 > > Change-Id: I8128ac96bcd2dc01b318c55843c4416bdd17c7ae > Reviewed-on: https://chromium-review.googlesource.com/1013318 > Commit-Queue: Alexei Filippov <alph@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52653} Bug: v8:7662 Change-Id: I28c5e693290057ad2bc90161c82419fb109ef1ae Reviewed-on: https://chromium-review.googlesource.com/1015747Reviewed-by:
Alexei Filippov <alph@chromium.org> Commit-Queue: Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#52678}
-
Leszek Swirski authored
Since external strings are used for things like source strings, we should tenure them from creation. Change-Id: I226ab9036836d76d8c17ed168ad97d7f0f824278 Reviewed-on: https://chromium-review.googlesource.com/1006961 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#52677}
-
Clemens Hammacher authored
The Cvtqui2ss and Cvtqui2sd methods did overwrite the {src} register and the given {tmp} register. This CL fixes this to avoid the overwrite of the {src} register, and to use the kScratchRegister instead of an explicitly passed tmp register. It also adds u32 -> f32/f64 conversions. All these methods can take either a register or an operand as src. This sometimes saves a mov operation. R=neis@chromium.org, ahaas@chromium.org Change-Id: I912a2a3b9d9c356f04ce51869a01c6fd11c76dd3 Reviewed-on: https://chromium-review.googlesource.com/1017121Reviewed-by:Andreas Haas <ahaas@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#52676}
-
Sigurd Schneider authored
Bug: v8:7659 Change-Id: Ib4a44eef02398482a969084f5004d6096e1fd979 Reviewed-on: https://chromium-review.googlesource.com/1017100Reviewed-by:
-
Erik Chen authored
Calls to madvise(MADV_FREE_REUSABLE) [when discarding/decommitting memory] should be paired with calls to madvise(MADV_FREE_REUSE) [when reusing/committing memory]. The latter is purely for accounting purposes. Bug: chromium:823915 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: Ib1758fd72c5ad4dfe731f5d9a6dbaf75b1e0e14b Reviewed-on: https://chromium-review.googlesource.com/988193 Commit-Queue: Erik Chen <erikchen@chromium.org> Reviewed-by:
-
Georg Neis authored
This turns most DCHECKs in the register allocator code into CHECKs, which hopefully will tell us more about the crashes in crbug 831822. This CL will eventually be reverted again. Bug: chromium:831822 Change-Id: I123ed507949ecab50bb0aaaf9e91978c9c2d8d65 Reviewed-on: https://chromium-review.googlesource.com/1016762 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#52673}
-
Marja Hölttä authored
BUG=v8:7308 Change-Id: I1976cd7e542a0304f6e14744e634c62dd06a83f5 Reviewed-on: https://chromium-review.googlesource.com/1014090 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#52672}
-
Peter Marshall authored
Previously when we put offsets into the SourcePositionTable, we added the header size of the code object as well. When we pull the positions out of the table (see ProfileGenerator::RecordTickSample) we already account for the header size. This means the offsets in the table should just be the offset of the PC within the actual code, not the offset within the code object, which is what we currently store. Currently this bug is probably not very noticeable, as it causes the reported line numbers to be slightly too low, but still within the same function. For a sampling profiler, we don't have any way to confirm which lines were actually sampled, so we don't notice that the results are wrong. The only way to see this bug is that there are some lines within a function (towards the end of the function) that we will never see ticks inside of, because the offset in the position table is not reachable with valid PC offsets. This CL removes the header size offset from values put into the source position table stored by the profiler. Bug: v8:7018 Change-Id: I00b17cec5f9c81d993d4e64c3c021052745a791e Reviewed-on: https://chromium-review.googlesource.com/1016560Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Georg Neis authored
Minidumps could potentially contain sensitive information, so we shouldn't be serving them to the world. R=machenbach@chromium.org Change-Id: Idb7a3c07c160e82d707a4abb857e098363da3345 Reviewed-on: https://chromium-review.googlesource.com/1015802Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#52670}
-
Ivica Bogosavljevic authored
Release 6 FP branch instruction contain branch delay slots so we can reenable them. Change-Id: I793b6acbcfd73f92c7e94ba99608616cc8d68199 Reviewed-on: https://chromium-review.googlesource.com/1016282Reviewed-by:
Sreten Kovacevic <sreten.kovacevic@mips.com> Commit-Queue: Sreten Kovacevic <sreten.kovacevic@mips.com> Cr-Commit-Position: refs/heads/master@{#52669}
-
Simon Zünd authored
This CL adds sort benchmarks for BigUint64Array and BigInt64Array. They form their own benchmark group separate from the Int and Float types/element kinds. R=jgruber@chromium.org Bug: v8:7382 Change-Id: Id3ce125be36a42c419a2632edc5f930547a1720e Reviewed-on: https://chromium-review.googlesource.com/1016643Reviewed-by:
-
Peter Marshall authored
This reverts commit 6c68efac. Reason for revert: https://bugs.chromium.org/p/v8/issues/detail?id=7668 Original change's description: > Reland "[heap] Move initial objects into RO_SPACE" > > This is a reland of f8ae62fe > > Original change's description: > > [heap] Move initial objects into RO_SPACE > > > > This moves: > > * the main oddballs (null, undefined, hole, true, false) as well as > > their supporting maps (also adds hole as an internalized string to make > > this work). > > * most of the internalized strings > > * the struct maps > > * empty array > > * empty enum cache > > * the contents of the initial string table > > * the weak_cell_cache for any map in RO_SPACE (and eagerly creates the > > value avoid writing to it during run-time) > > > > The StartupSerializer stats change as follows: > > > > RO_SPACE NEW_SPACE OLD_SPACE CODE_SPACE MAP_SPACE LO_SPACE > > old 0 0 270264 32608 12144 0 > > new 21776 0 253168 32608 8184 0 > > Overall memory usage has increased by 720 bytes due to the eager > > initialization of the Map weak cell caches. > > > > Also extends --serialization-statistics to print out separate instance > > type stats for objects in RO_SPACE as shown here: > > > > Read Only Instance types (count and bytes): > > 404 16736 ONE_BYTE_INTERNALIZED_STRING_TYPE > > 2 32 HEAP_NUMBER_TYPE > > 5 240 ODDBALL_TYPE > > 45 3960 MAP_TYPE > > 1 16 BYTE_ARRAY_TYPE > > 1 24 TUPLE2_TYPE > > 1 16 FIXED_ARRAY_TYPE > > 1 32 DESCRIPTOR_ARRAY_TYPE > > 45 720 WEAK_CELL_TYPE > > > > Bug: v8:7464 > > Change-Id: I12981c39c82a7057f68bbbe03f89fb57b0b4c6a6 > > Reviewed-on: https://chromium-review.googlesource.com/973722 > > Commit-Queue: Dan Elphick <delphick@chromium.org> > > Reviewed-by: Hannes Payer <hpayer@chromium.org> > > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > > Reviewed-by: Yang Guo <yangguo@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#52435} > > Bug: v8:7464 > Change-Id: I50427edfeb53ca80ec4cf46566368fb2213ccf7b > Reviewed-on: https://chromium-review.googlesource.com/999654 > Commit-Queue: Dan Elphick <delphick@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Reviewed-by: Hannes Payer <hpayer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52638} TBR=rmcilroy@chromium.org,yangguo@chromium.org,hpayer@chromium.org,mlippautz@chromium.org,delphick@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:7464,v8:7668 Change-Id: I10aa03623b51e997f95a3715ea9f0bf5d29d2cdb Reviewed-on: https://chromium-review.googlesource.com/1016600 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#52667}
-
Simon Zünd authored
The escaped double quote is needed for calling CSA macros that expect const char* (so the double quotes are preserved). Example: type MethodName; const kProtoSort: MethodName = '\"%TypedArray%.prototype.sort\"'; extern macro ValidateTypedArray(Context, Object, MethodName): JSTypedArray; R=danno@chromium.org Bug: v8:7382 Change-Id: Ida554f7d2638fda2c9e1ace9975c3744b5d84050 Reviewed-on: https://chromium-review.googlesource.com/1016400Reviewed-by:
Daniel Clifford <danno@chromium.org> Commit-Queue: Simon Zünd <szuend@google.com> Cr-Commit-Position: refs/heads/master@{#52666}
-
Stephan Herhut authored
This is a reland of 4d7ad46d Original change's description: > Introduce CodeReference > > Add a struct CodeReference that can be stack allocated to pass a > reference to either an on-heap code object or off-heap WasmCode object > in a gc safe manner. The struct also provides a common interface such > that code can be written independently of the kind of code object it > references. > > Change-Id: I5a6f74462e6e141d167c7fd9bac8c21941fd83b1 > Reviewed-on: https://chromium-review.googlesource.com/977905 > Commit-Queue: Stephan Herhut <herhut@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52580} Change-Id: I40861474fe4a3efd72e6c59e2e7b847ab6772735 Reviewed-on: https://chromium-review.googlesource.com/1013939 Commit-Queue: Stephan Herhut <herhut@chromium.org> Reviewed-by:
-
Sigurd Schneider authored
Change-Id: Ic942391ba5eca97f09bb5f9b89aef0630094c77c Reviewed-on: https://chromium-review.googlesource.com/1015100Reviewed-by:
-
Sigurd Schneider authored
The framestate is necessary, because the PerformPromiseThen builtin calls into the runtime function PromiseRevokeReject, which ultimately calls back into the embedder. Node may execute JavaScript in the callback, and the missing framestate can then make our stack frame walker unhappy. Bug: v8:7659 Change-Id: I47391fd2b9b3c10ef26204a41e58f8082243c702 Reviewed-on: https://chromium-review.googlesource.com/1015361Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#52663}
-
Clemens Hammacher authored
This implement float to i32/u32 conversions on ia32 and x64. R=ahaas@chromium.org Bug: v8:6600 Change-Id: I4eb6a74d86fafce3245bf3f37d32ac6ca156550a Reviewed-on: https://chromium-review.googlesource.com/1014123Reviewed-by:
-
Simon Zünd authored
This change is in preparation for implementing TypedArray builtins in torque. Torque makes assumptions about naming conventions regarding file and class names, which are currently inconsistent for TypedArrays. The class is called TypedArrayBuiltinsAssembler while the current file name suggests Typedarray... . R=jgruber@chromium.org Bug: v8:7382 Change-Id: I3051dacb2bfbb7041482c8aa0a1104776ab4972c Reviewed-on: https://chromium-review.googlesource.com/1016300Reviewed-by:
-
Mike Stanton authored
In ArrayBuiltinsAssembler::VisitAllFastElementsOneKind(), we enumerate an arrays elements, carefully checking for the "hole" when required. This code is only called for arrays whose prototype is the initial array prototype. And the path is only available when the initial array prototype is free of elements. Since that's the case, we only need to verify that the initial array prototype remains free of elements during an iteration with javascript callbacks. We don't need a body of code that can walk the prototype chain looking for elements visible through the "hole" value. In practice, this code was never run. Change-Id: Iba5e275c559d495aa1cf6a4f29d66e2ce475c981 Reviewed-on: https://chromium-review.googlesource.com/1015023 Commit-Queue: Michael Stanton <mvstanton@chromium.org> Reviewed-by:
-
Michael Achenbach authored
NOTRY=true TBR=sergiyb@chromium.org Bug: chromium:830557 Change-Id: I61510297e5195eb74425c71e41c4d95f080a280d Reviewed-on: https://chromium-review.googlesource.com/1016420Reviewed-by:
-
Marja Hölttä authored
This is also pre-work for in-place weak refs. BUG=v8:7308, v8:5988 Change-Id: Ie78b0c59695c1e6af9780fffb363c931e2ee34e2 Reviewed-on: https://chromium-review.googlesource.com/1013583 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#52658}
-
Michael Achenbach authored
Prepares for: https://crrev.com/c/1015000 NOTRY=true Bug: chromium:830557 Change-Id: I51c12867d95de19350e0e55aaf097bbb479348dc Reviewed-on: https://chromium-review.googlesource.com/1015004 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#52657}
-
Michael Achenbach authored
Each builder now uses a dict to specify tests with a 'tests' key. This will allow adding other builder-specific keys in follow ups. Prepared on infra side by: https://crrev.com/c/1013713 Bug: chromium:830557 Change-Id: I1dd799cdfcc029ab22de813b7869abe982047e0f Reviewed-on: https://chromium-review.googlesource.com/1013979Reviewed-by:
-
Christian O. Andersson authored
There are various situations where we explicitly compare a SMI against another SMI (e.g., BuildIndexedJump). This is also a common pattern for generated code (e.g., comparing a loop variable with an integer). Instead of using the generic equality/strict-equality stub for this, which is expensive, this CL offers a simple comparison stub, repurposing the TestEqualStrictNoFeedback bytecode to TestReferenceEqual Bug: v8:5310 Change-Id: Ib2b47cd24d5386cf0d20d3bd794776dc6e3a02a5 Reviewed-on: https://chromium-review.googlesource.com/1007542Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Christian O. Andersson <cricke@chromium.org> Cr-Commit-Position: refs/heads/master@{#52655}
-
- 17 Apr, 2018 16 commits
-
-
Michael Achenbach authored
This reverts commit 9a19ce25. Reason for revert: https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20TSAN/builds/20359 Original change's description: > [profiler] Ensure there's a single ProfilerListener per isolate. > > BUG=v8:7662 > > Change-Id: I8128ac96bcd2dc01b318c55843c4416bdd17c7ae > Reviewed-on: https://chromium-review.googlesource.com/1013318 > Commit-Queue: Alexei Filippov <alph@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52653} TBR=alph@chromium.org,yangguo@chromium.org Change-Id: I3c3b6eb8d6f9911fa318f24a2e6e74180b83398e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7662 Reviewed-on: https://chromium-review.googlesource.com/1015561Reviewed-by:
-
Alexei Filippov authored
BUG=v8:7662 Change-Id: I8128ac96bcd2dc01b318c55843c4416bdd17c7ae Reviewed-on: https://chromium-review.googlesource.com/1013318 Commit-Queue: Alexei Filippov <alph@chromium.org> Reviewed-by:
-
Ingvar Stepanyan authored
Previously, if an unbound script was created in a non-inspected context, but later bound to an inspected one, it never appeared in the debugger sources. After this change `OnAfterCompile` will be invoked not on the original script compilation, but when it's actually bound to a context for execution, which means `Debugger.scriptParsed` will be now sent to the inspector even for such precompiled scripts. R=jgruber@chromium.org, kozyatinskiy@chromium.org, yangguo@chromium.org Bug: v8:7654 Change-Id: Ice13312e425903fb2baf14edab5c566d649a6438 Reviewed-on: https://chromium-review.googlesource.com/1013581Reviewed-by:
-
Junliang Yan authored
R=jarin@chromium.org, mstarzinger@chromium.org Bug=v8:7651 Change-Id: I4007c6de83806c2aad8fc105331986bfcf709033 Reviewed-on: https://chromium-review.googlesource.com/1012460 Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#52651}
-
Jakob Kummerow authored
One more place behind a non-default build flag that needs updating after the recent Address typedef change. Change-Id: Ica5022966e7773c621624d1cd5c20296c52c0b39 Reviewed-on: https://chromium-review.googlesource.com/1014320Reviewed-by:
-
Andreas Haas authored
In a recent CL (https://crrev.com/c/1012039) I removed the only valid use case of {external_reference_redirector}. In this CL I remove the remaining uses, which are more or less checks if there is a simulator or not. R=mstarzinger@chromium.org Change-Id: I96203b7b112d57bb3feb9d6863b036747b1963f0 Reviewed-on: https://chromium-review.googlesource.com/1014126 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#52649}
-
Andreas Haas authored
With this CL we do the redirection of ExternalReferences for simulators independent of the isolate but instead use the redirector provided by the simulator directly. Thereby we make the code independent of the isolate. I plan to remove the redirector from the isolate in a separate CL. R=mstarzinger@chromium.org Change-Id: I2ae0b2184da214cf7606fabeabc9bec35bf0616e Reviewed-on: https://chromium-review.googlesource.com/1012039Reviewed-by:
-
sreten.kovacevic authored
These tests fail since instructions were implemented in Liftoff. Problem was with NaN cases, where additional job has to be done on MIPS r2, r1 and Longsoon. Change-Id: Id02462aa08e79b03d66b5083b81f19dc1c88cc3e Reviewed-on: https://chromium-review.googlesource.com/1015001Reviewed-by:
Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Commit-Queue: Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Cr-Commit-Position: refs/heads/master@{#52647}
-
Sathya Gunasekaran authored
Class fields needs to be initialized after `this` is bound, as per the new spec change: https://github.com/tc39/proposal-class-fields/pull/92 This CL moves the initialization of `this` from parser desugaring to the bytecode generator. Bug: v8:7647 Change-Id: I20f749403e5a4d2f06a39726cf39012ceb541987 Reviewed-on: https://chromium-review.googlesource.com/1014383Reviewed-by:
Mythri Alle <mythria@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#52646}
-
Georg Neis authored
R=bmeurer@chromium.org Change-Id: I06b889333fe6481d4704138031ce6de0fcf70a4c Reviewed-on: https://chromium-review.googlesource.com/1013715Reviewed-by:
-
Georg Neis authored
Throw a TypeError if the length of a concat-spreadable object makes the total length too large, as specified. Bug: v8:7652 Change-Id: Ie3f694d64c949703edd733c0310cfb3f64b78a15 Reviewed-on: https://chromium-review.googlesource.com/1013714Reviewed-by:
-
Yang Guo authored
Flattening the string upfront has performance benefits and we can also simplify the implementation quite a bit. Bug: v8:6780 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: Ic75bdfdf900d30e51e95cdf1cb8d09aab06332c6 Reviewed-on: https://chromium-review.googlesource.com/1014102Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#52643}
-
sreten.kovacevic authored
Refactor AddPair and SubPair Macro-assembler instructions to prevent register overwriting, refactor all the places where these instructions are used. Also, implement MulPair instruction. Change-Id: I3f8f9d5fe6fa5bf25df3446614ac311cf886b6ac Reviewed-on: https://chromium-review.googlesource.com/1013571Reviewed-by:
-
Sigurd Schneider authored
This is a reland of 370d95dc Original change's description: > [turbofan] Enable Promise constructor inlining by default > > Bug: v8:7584 > Change-Id: I7443c28c74676ee1f27550674c8f712594e21cc7 > Reviewed-on: https://chromium-review.googlesource.com/992314 > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Sigurd Schneider <sigurds@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52341} Bug: v8:7584 Change-Id: Ie33b89bf8bb7abde426d477a8b39914e6d90e5b6 Reviewed-on: https://chromium-review.googlesource.com/1009862 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
jgruber authored
TBR=yangguo@chromium.org No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:6666 Change-Id: I051dd5a1578d2e611f4b6351aa9cff9451494a5c Reviewed-on: https://chromium-review.googlesource.com/1013711 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Sergiy Byelozyorov authored
R=machenbach@chromium.org No-Try: true Bug: chromium:793687 Change-Id: I6d2988a0a2644de806e7b273ed5ff9213fceda5d Reviewed-on: https://chromium-review.googlesource.com/1013708 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
-
