- 24 May, 2018 25 commits
-
-
Tobias Tebbi authored
Change-Id: Ie8bdbcdea8006d3105c419113f9adb2c1d6f162c Reviewed-on: https://chromium-review.googlesource.com/1070203 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#53341}
-
Michael Starzinger authored
The RelocInfo::RUNTIME_ENTRY relocation mode is only used for deopt points in JavaScript code and should never appear in WebAssembly code. R=titzer@chromium.org Change-Id: Ied1d61e2b1eb886565d13448442dd6a6ed35d3f0 Reviewed-on: https://chromium-review.googlesource.com/1070197Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#53340}
-
Théotime Grohens authored
This CL completely removes the C++ builtin implementation of the DataView.prototype.buffer, DataView.prototype.byteLength, and DataView.prototype.byteOffset getters, and moves them to a Torque implementation (that still relies on a bit of CSA). Change-Id: Id46678ae709c3787b7b93d0f78bd2a6e16e00f7b Reviewed-on: https://chromium-review.googlesource.com/1070369 Commit-Queue: Théotime Grohens <theotime@google.com> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#53339}
-
Sigurd Schneider authored
Bug: chromium:846000 Change-Id: If74749f11c7e1e112090a18f79ebed1819535d24 Reviewed-on: https://chromium-review.googlesource.com/1071671Reviewed-by:
-
Sigurd Schneider authored
Bug: v8:7783 Change-Id: If351c07735b583816389b77d4077b3494571626f Reviewed-on: https://chromium-review.googlesource.com/1071441 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#53337}
-
Sigurd Schneider authored
Bug: v8:7783 Change-Id: I49a6d1a4b22dcfdda206b1c00cfff16310a0458c Reviewed-on: https://chromium-review.googlesource.com/1071609 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#53336}
-
Sigurd Schneider authored
Bug: v8:7783 Change-Id: I69e3744a40eeebb5fb4592a4ae56efbb7cb762a8 Reviewed-on: https://chromium-review.googlesource.com/1069354 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#53335}
-
Jaroslav Sevcik authored
Change-Id: I485e6ef79fb641ca1db0784433b0866c91a382b8 Reviewed-on: https://chromium-review.googlesource.com/1071442Reviewed-by:
-
Sigurd Schneider authored
The slow test tests SmiLexicographicCompare on a large number of Smi comparisons; we can disable this test for some debug/noopt builds without losing much coverage. Bug: v8:7783 Change-Id: Iab40e596604bb957b4d3312073ad85dbac08c6a0 Reviewed-on: https://chromium-review.googlesource.com/1068190 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Simon Zünd authored
R=petermarshall@chromium.org Change-Id: Id27cae79dcd82b6dd7790736169c76e89ae8881d Reviewed-on: https://chromium-review.googlesource.com/1071428 Commit-Queue: Simon Zünd <szuend@google.com> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#53332}
-
Simon Zünd authored
R=tebbi@chromium.org Change-Id: Id524c8239f99fc26ac5cd19cbdea39dba62f2c3f Reviewed-on: https://chromium-review.googlesource.com/1071650Reviewed-by:
-
Peter Marshall authored
We store deopt inline frames for all functions when we receive the code creation event. We only ever use this information for code which is deoptimized. Given that we receive code deopt events, we can just store this information when the code is deoptimized. At the time of the code deopt event, we also know the associated deopt_id. That means we don't need to store a map of deopt_ids to vectors of frames, because we will only ever access the frames for the deopt_id that is already set. This means we store way less data, particularly for long-running processes which see fewer deopts. This saves 10MiB peak memory on the node server example. Bug: v8:7719 Change-Id: If6cf5ec413848e4c9f3c1e2106366ae2adae6fb1 Reviewed-on: https://chromium-review.googlesource.com/1050289 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#53330}
-
Peter Marshall authored
This distinction doesn't matter, they aren't treated any differently to other strings. Change-Id: I524a0a1c4089284af97aa507afc5bd5985fe6631 Reviewed-on: https://chromium-review.googlesource.com/1071628Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#53329}
-
Marja Hölttä authored
Moving them away was a mistake. Fixing this enables getting rid of a bunch of includes. BUG=v8:5402 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: I5482eab4281c7450350f058fe0a04a6f375ea082 Reviewed-on: https://chromium-review.googlesource.com/1070188Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#53328}
-
Jaroslav Sevcik authored
Currently, we context allocate all parameters for generators. With this CL, we keep arguments on stack (unless they escape to inner closure) and copy them between the stack and the generator's register file on suspend/resume. This will save context allocation in most cases. Note: There is an asymmetry between suspend and resume. - Suspend copies arguments and registers to the generator. - Resume copies only the registers from the generator, the arguments are copied by the ResumeGenerator trampoline. Bug: v8:5164 Change-Id: I6333898c60abf461b1ab1b5c6d3dc7188fa95649 Reviewed-on: https://chromium-review.googlesource.com/1063712 Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#53327}
-
Miran.Karic authored
The timeout in the test is close to execution time in debug mode so it fails occasionally. The test is measuring array slice algorithm performance but changes unrelated to it affect the test result in debug mode, therefore it should be skipped. BUG=v8:7726 TEST=regress/regress-165637 Change-Id: Ib330d8e3c0d3f6a1150ccb59b60d17a41b87df87 Reviewed-on: https://chromium-review.googlesource.com/1071576 Commit-Queue: Miran Karić <miran.karic@mips.com> Reviewed-by:
-
Dan Elphick authored
Removes uses of HeapObject::GetIsolate()/GetHeap() from VerifyPointersVisitor by adding it to the visitor at construction time. Bug: v8:7786 Change-Id: I28388f2eadbaf9947eafe0c62492c9a4781be250 Reviewed-on: https://chromium-review.googlesource.com/1071575Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#53325}
-
Michael Hablich authored
TBR=machenbach@chromium.org NOTRY=true Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: I045123269afe02302d6b7823ba431fa735312000 Reviewed-on: https://chromium-review.googlesource.com/1070978 Commit-Queue: Michael Hablich <hablich@chromium.org> Reviewed-by:
Michael Hablich <hablich@chromium.org> Cr-Commit-Position: refs/heads/master@{#53324}
-
Stephan Herhut authored
This adds basic support to emit wasm disassembly to the json files digested by turbolizer. Change-Id: Icd8fc92e9539dc336879ef6da76e31890b95e40e Reviewed-on: https://chromium-review.googlesource.com/1069275 Commit-Queue: Stephan Herhut <herhut@chromium.org> Reviewed-by:
-
Simon Zünd authored
This CL uses the new function pointers and generic features of Torque to improve the performance of TypedArray.p.sort. Instead of one Load/Store builtin that dispatches at runtime based on the element kind, there are now many small builtins (one for each element kind). The sorting algorithm then uses function pointers to those small builtins, which get set once. Changes in the relevant benchmarks: Benchmark Original (JS) Current This CL IntTypes 83.9 202.3 240.7 BigIntTypes 32.1 47.2 53.3 FloatTypes 99.3 109.3 129.3 Bug: v8:7382 Change-Id: I8684410524d546615b19f6edcbfdc615068196aa Reviewed-on: https://chromium-review.googlesource.com/1070069 Commit-Queue: Simon Zünd <szuend@google.com> Reviewed-by:
-
Sigurd Schneider authored
Bug: v8:7754 Change-Id: Ifa329efa1ccbae3d4cf6251f43b11b697ddf76f8 Reviewed-on: https://chromium-review.googlesource.com/1068678 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Georg Neis authored
Instead use the canonical empty fixed array. Some code assumes that this is the only fixed array of length 0. Bug: chromium:843062 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: If780acf50147c061a81f2ff2b31779fbd1c78559 Reviewed-on: https://chromium-review.googlesource.com/1064052Reviewed-by:
-
Sigurd Schneider authored
Bug: v8:7779 Change-Id: I79471ecb038b710d21e938efd3f9207da30e6622 NOTRY=true Change-Id: I79471ecb038b710d21e938efd3f9207da30e6622 Reviewed-on: https://chromium-review.googlesource.com/1071508 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Michael Lippautz authored
Bug: v8:7760 Change-Id: I5589b873845d614a4751b12319c61c91aae04a84 Reviewed-on: https://chromium-review.googlesource.com/1070829Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#53318}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/4389c9c..1e1a86d Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/12f7d6b..1986f5a TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I70e535a4ac787454f82d8d3f4ef57c2bcb57e564 Reviewed-on: https://chromium-review.googlesource.com/1071187Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#53317}
-
- 23 May, 2018 15 commits
-
-
Aseem Garg authored
R=gdeepti@chromium.org,bbudge@chromium.org,clemensh@chromium.org,titzer@chromium.org BUG=v8:6020 Change-Id: I671d74b49206a3612764c7b9cb63591e7e81e857 Reviewed-on: https://chromium-review.googlesource.com/1069933 Commit-Queue: Aseem Garg <aseemgarg@chromium.org> Reviewed-by:
-
Mathias Bynens authored
Bug: v8:7220 Change-Id: I9fef685f19cadbe87cd6451fe887f4c9c7d23b19 Reviewed-on: https://chromium-review.googlesource.com/1070337 Commit-Queue: Mathias Bynens <mathias@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#53315}
-
Alexei Filippov authored
The patch makes it manage a free list of released code_entries_ slots, and reuse the slots as needed. BUG=v8:7719 Change-Id: I07df1ce983fe00e0ca3d1a1ea20e1a141aabad99 Reviewed-on: https://chromium-review.googlesource.com/1062769Reviewed-by:
-
Alexei Filippov authored
BUG=chromium:844150 Change-Id: I0f7e10fb9778b3de76591ad4819be45c8c50c8d4 Reviewed-on: https://chromium-review.googlesource.com/1064815Reviewed-by:
Stephan Herhut <herhut@chromium.org> Commit-Queue: Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#53313}
-
Théotime Grohens authored
This CL adds a baseline Torque implementation of the DataView getters and setters. Right now, the Torque code just calls the C++ implementation, which has moved to runtime. Change-Id: Ic96fde7ea908c628af9586e84511037c237c4d3b Reviewed-on: https://chromium-review.googlesource.com/1061520Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Théotime Grohens <theotime@google.com> Cr-Commit-Position: refs/heads/master@{#53312}
-
Marja Hölttä authored
Since the StubCache it's cleared at the end of the GC, it doesn't matter if it contains weak or strong pointers. BUG=v8:7308 Change-Id: Ib141e3d411523c67ccb8f8979845a88488d6e4ee Reviewed-on: https://chromium-review.googlesource.com/1064053 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
-
Michael Lippautz authored
Bug: v8:7760 Change-Id: I975b467e46bed684e141c2a78a396de1072125f1 Reviewed-on: https://chromium-review.googlesource.com/1068894Reviewed-by:
-
Simon Zünd authored
This CL replaces the default ConsoleErrorListener with a custom one. The only difference is that the error message now also includes the file name where the lexer/parser error happened. R=tebbi@chromium.org Change-Id: Ifa22501a55066b82b32234c76df180db41ee8b62 Reviewed-on: https://chromium-review.googlesource.com/1069137 Commit-Queue: Simon Zünd <szuend@google.com> Reviewed-by:
-
Simon Zünd authored
This CL stops torque from crashing when a function pointer call site uses wrong parameters. R=tebbi@chromium.org Change-Id: If097d0882ca5370e525097c68014f7ec051b3fe8 Reviewed-on: https://chromium-review.googlesource.com/1068181Reviewed-by:
-
Tobias Tebbi authored
Bug: v8:7784 Change-Id: Ie4bbecacc9bced842269871dd5efa5113e09059d Reviewed-on: https://chromium-review.googlesource.com/1070200Reviewed-by:
-
Michael Achenbach authored
Also mark another slow tests as SLOW. TBR=jgruber@chromium.org Bug: v8:7783 Change-Id: I69a8ac82e7898fa3b374c5b66a441f040d241413 Reviewed-on: https://chromium-review.googlesource.com/1069093Reviewed-by:
-
Camillo Bruni authored
This reverts commit 05bcb12e. Reason for revert: Causes isolate startup regressions (https://crbug.com/845508) Original change's description: > Flush ICache on startup deserialization after marking memory executable > > Tentative fix for Android invoke crashers with write protection code > enabled. > > Bug: chromium:842862 > Change-Id: If238b25b239b50c597f3745aa683f564a717434f > Reviewed-on: https://chromium-review.googlesource.com/1061513 > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Camillo Bruni <cbruni@chromium.org> > Cr-Commit-Position: refs/heads/master@{#53209} TBR=mstarzinger@chromium.org,cbruni@chromium.org,jgruber@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:842862, chromium:845508, chromium:845877 Change-Id: Iff002e1ac75aca48c696053dddf1b413f372629e Reviewed-on: https://chromium-review.googlesource.com/1068048 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Michael Achenbach authored
NOTRY=true TBR=jgruber@chromium.org Change-Id: Iac18f84235fe2013c3ffb3af56f95827082fa73a Reviewed-on: https://chromium-review.googlesource.com/1070201Reviewed-by:
-
Jaroslav Sevcik authored
This is based on https://chromium-review.googlesource.com/c/v8/v8/+/940174. It is fine to use the more complex addressing modes here because our poisoning does not poison indexes anymore (it poisons value instead). Bug: chromium:839789 Change-Id: I818a060f835f7dea842cb855d077e871a95b2c01 Reviewed-on: https://chromium-review.googlesource.com/1065773 Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
-
Hannes Payer authored
Change-Id: I1b4568123a8ad55804266c40b988b39362ba7aa4 Reviewed-on: https://chromium-review.googlesource.com/1070157Reviewed-by:
-
