- 06 Apr, 2018 38 commits
-
-
jgruber authored
Bug: v8:7626 Change-Id: Ifd6908941b7bc62357c3577bea4a097c45903129 Reviewed-on: https://chromium-review.googlesource.com/998167Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52453}
-
Alexey Kozyatinskiy authored
This is a reland of 0340874b Original change's description: > [debug] add runtime side effect check for StaCurrentContextSlot > > R=yangguo@chromium.org > > Bug: v8:7588 > Change-Id: If78f6dd460c7423923800a98d44520c1bf71663c > Reviewed-on: https://chromium-review.googlesource.com/996236 > Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52398} Bug: v8:7588 Change-Id: Ife6b039ea3291103a54ae04c3007fe4610371c3f Reviewed-on: https://chromium-review.googlesource.com/998801Reviewed-by:
Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#52452}
-
Clemens Hammacher authored
The maximum number of background tasks to spawn can be computed right in the constructor of the CompilationState, and is constant afterwards. Additionally, we ensure to never start more background tasks than the number of available compilation units. R=ahaas@chromium.org Change-Id: I430e9a28a0bd15166ed05d120782f182d10c3e44 Reviewed-on: https://chromium-review.googlesource.com/997652 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#52451}
-
Ben L. Titzer authored
R=mstarzinger@chromium.org Bug: v8:7424 Change-Id: I5a854d334957c285eebe850024c25d1cdcf71f7f Reviewed-on: https://chromium-review.googlesource.com/995772 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#52450}
-
Junliang Yan authored
Port b158bfdc Original Commit Message: This is a reland of 63ecddc8 Original change's description: > [runtime] Remove the construct_stub field of the SFI > > Don't dispatch based on the construct_stub field anymore. Rather than > read it out and jump to the construct stub, we can switch on the > builtin_id. > > Builtins will always have builtin_id as a Smi, so this signals we need > to jump to JSBuiltinsConstructStub. The only exception is for uncompiled > functions, which will have kCompileLazy as the builtin_id, but need to > jump to the generic stub instead. > > API function calls will have a FunctionTemplateInfo in the SFI > function_data field, and need to go to the builtins stub as well. > > The final case is everything else, which should go to the generic stub. > > Bug: v8:7503 > Change-Id: I14790a5f9784dc0d940bf10a05f5310026e1d482 > Reviewed-on: https://chromium-review.googlesource.com/980941 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> > Commit-Queue: Peter Marshall <petermarshall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52345} R=petermarshall@chromium.org, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I53d92ea7326c5a0ffec25eef0972cdeb659848b6 Reviewed-on: https://chromium-review.googlesource.com/998018Reviewed-by:
Joran Siu <joransiu@ca.ibm.com> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#52449}
-
Igor Sheludko authored
1) Add exit point parameter to EmitGenericPropertyStore(), 2) carve TryLookupPropertyInSimpleObject() out of TryLookupProperty(). Bug: v8:5988 Change-Id: I6cef48731c27e5bb72dce5eaa0169fbf59787ed7 Reviewed-on: https://chromium-review.googlesource.com/997747Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#52448}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/647f86b..d1cd744 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/buildtools/+log/3748a2a..10d701f Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/b1c9ad5..aaeb23e Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/82ac1c9..cd83d95 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ib6e4745827cc54412062558c1f7272fc56143518 Reviewed-on: https://chromium-review.googlesource.com/999329 Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#52447}
-
Igor Sheludko authored
... in favor of SelectConstant(). Bug: chromium:829679 Change-Id: Ic7cc887254b4f6b29339b06c5782d71f77d3c9a5 Reviewed-on: https://chromium-review.googlesource.com/999601Reviewed-by:
-
Clemens Hammacher authored
If --wasm-num-compilation-tasks is set to 0, we spawn all background tasks as foreground tasks. Semantically, they are still treated like background tasks, but they will execute interleaved with the foreground tasks. This should not deadlong since all foreground tasks eventually return to the event loop. R=ahaas@chromium.org Bug: chromium:829681 Change-Id: Id57cbb10157c085acd57a3d30a0a43c824a64591 Reviewed-on: https://chromium-review.googlesource.com/999594Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#52445}
-
Sergiy Byelozyorov authored
R=machenbach@chromium.org Change-Id: I45a6b7ef7b185c0bc05185672383c682b6e1e798 Reviewed-on: https://chromium-review.googlesource.com/998153 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
-
Yang Guo authored
TBR=machenbach@chromium.org Change-Id: Icbba06aefb728ebc7e2f04fa9992d51e0589a33b Reviewed-on: https://chromium-review.googlesource.com/999596Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
-
Igor Sheludko authored
Given that we got a store transition handler for free (because it's just a transition map) there's no need to wait for a second "use" of that transition in order to install a normal store transition handler. Bug: v8:5988 Change-Id: Iecdcfdd096a8efffdd0662f1b1d604943e57d85a Reviewed-on: https://chromium-review.googlesource.com/997553Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#52442}
-
Peter Marshall authored
Also changed the order of params so that context comes first to be more consistent with other CSA helpers. Change-Id: Ibf602dc7f3a148bed7fc0f93cc3dbc714febd786 Reviewed-on: https://chromium-review.googlesource.com/999513Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#52441}
-
Michael Achenbach authored
This reverts commit f8ae62fe. Reason for revert: https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20-%20internal%20snapshot/builds/14825 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} TBR=rmcilroy@chromium.org,yangguo@chromium.org,hpayer@chromium.org,mlippautz@chromium.org,delphick@chromium.org Change-Id: Ie62a73a5be3b21a15bb46e342acb3e808fbaa4f3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7464 Reviewed-on: https://chromium-review.googlesource.com/999653Reviewed-by:
-
Michael Achenbach authored
NOTRY=true TBR=clemensh@chromium.org Change-Id: Ifc171886d122ca19230a3099cf14f13a4bfcabb1 Reviewed-on: https://chromium-review.googlesource.com/999515Reviewed-by:
-
Clemens Hammacher authored
Test that Managed objects get collected if they are not referenced any more. R=ulan@chromium.org Bug: v8:7628 Change-Id: I4a594ebe835071d76d7a6e2ddee6a6092b3e4a31 Reviewed-on: https://chromium-review.googlesource.com/999482Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#52438}
-
Michael Achenbach authored
NOTRY=true Bug: chromium:829681 Change-Id: Iccf9b190e77b1c27fedec74d67f5948803dd1fa9 Reviewed-on: https://chromium-review.googlesource.com/998355Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#52437}
-
Ben L. Titzer authored
This change makes lifetime management of WasmCode much simpler. By using the WasmInstanceObject as the context for WASM code execution, including the pointer to the memory base and indirect function tables, this keeps the instance alive when WASM code is on the stack, since the instance object is passed as a parameter and spilled onto the stack. This is in preparation of sharing the code between instances and isolates. Bug: v8:7424 R=mstarzinger@chromium.org Change-Id: Ia35a3ce91a8f6135767fa764e185cde8bbc889f4 Reviewed-on: https://chromium-review.googlesource.com/997932 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
-
Dan Elphick authored
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:
-
Michael Achenbach authored
NOTRY=true TBR=sergiyb@chromium.org Bug: chromium:829774 Change-Id: I85ea46a68f620dfd7db04e881b6363ef260392f7 Reviewed-on: https://chromium-review.googlesource.com/999490Reviewed-by:
-
Michael Starzinger authored
Now that all WebAssembly code (including its lazy compile stub) has been moved off the garbage-collected heap, we can determine the taggedness of parameters purely from the {Code::Kind} and no longer need a dedicated flag for it. R=clemensh@chromium.org BUG=v8:6792 Change-Id: If40b6763d042c19b937391fac8301a03b8ccc891 Reviewed-on: https://chromium-review.googlesource.com/999416Reviewed-by: -
Michael Achenbach authored
This will allow setting v8_debug from within a Chromium release bot. Bug: chromium:828846 Change-Id: I714291feaa9ba90daba871ca9a12e6651bcd7dfa Reviewed-on: https://chromium-review.googlesource.com/999486 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#52432}
-
Michael Achenbach authored
This reverts commit cfd7df1b. Reason for revert: Seems to flush out more problems: https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20-%20cfi/builds/14390 Original change's description: > Reland "Enable cfi-icall on the v8 CFI bots" > > This is a reland of 9a7e9cf2 > > Original change's description: > > Enable cfi-icall on the v8 CFI bots > > > > BUG=v8:7164 > > > > Change-Id: I7522ba6ac2bde89c84bcd49bc116a432091a2938 > > Reviewed-on: https://chromium-review.googlesource.com/990802 > > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > > Reviewed-by: Clemens Hammacher <clemensh@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#52343} > > Bug: v8:7164 > Change-Id: Ia883adedf9d54e4a2518d66c85799354d930990e > Reviewed-on: https://chromium-review.googlesource.com/996133 > Reviewed-by: Clemens Hammacher <clemensh@chromium.org> > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52425} TBR=machenbach@chromium.org,clemensh@chromium.org,vtsyrklevich@chromium.org Change-Id: I5a45756f7e2e74ac50ae9fb93716b9083cdf4379 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7164 Reviewed-on: https://chromium-review.googlesource.com/999633Reviewed-by:
-
Clemens Hammacher authored
Remove redundant argument, add a DCHECK and explicitly specify the capture list of the lambdas. R=ahaas@chromium.org Bug: v8:7570 Change-Id: I09fc6004ffc5cdc7b4c153748ed95e86ae85aaa2 Reviewed-on: https://chromium-review.googlesource.com/998098Reviewed-by:
-
Dan Elphick authored
When serializing/deserializing RO_SPACE objects in CodeSerializer use BackReferences to avoid re-allocating inside RO_SPACE. Change-Id: Ie9063a43a4f758f0401ad59dfcc61c4b759591bc Reviewed-on: https://chromium-review.googlesource.com/997837 Commit-Queue: Dan Elphick <delphick@chromium.org> Reviewed-by:
-
Jakob Gruber authored
This reverts commit 0340874b. Reason for revert: Tentative revert for https://crbug.com/v8/7626 Original change's description: > [debug] add runtime side effect check for StaCurrentContextSlot > > R=yangguo@chromium.org > > Bug: v8:7588 > Change-Id: If78f6dd460c7423923800a98d44520c1bf71663c > Reviewed-on: https://chromium-review.googlesource.com/996236 > Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52398} TBR=yangguo@chromium.org,kozyatinskiy@chromium.org Change-Id: I77a679649a6149607aefd44f6b7f3f6dfe548776 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7588 Reviewed-on: https://chromium-review.googlesource.com/998036Reviewed-by:
-
Simon Zünd authored
Inlines nameOrSourceURL and locationFromPosition of the Script object at call sites. R=jgruber@chromium.org Bug: v8:7624 Change-Id: If217d4c1412fa22aaa856a017f73be4c803e70ac Reviewed-on: https://chromium-review.googlesource.com/997741 Commit-Queue: Simon Zünd <szuend@google.com> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Michael Lippautz authored
The byte_length of ArrayBuffers may be a heap number. This length is needed for freeing a buffer during tear down, implying that ArrayBuffers need to be freed before regular space tear down can remove actual pages. Bug: v8:7623 Change-Id: Iab91843e48c50276a2e110915f69cf9e6c24ef8f Reviewed-on: https://chromium-review.googlesource.com/997776 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Vlad Tsyrklevich authored
This is a reland of 9a7e9cf2 Original change's description: > Enable cfi-icall on the v8 CFI bots > > BUG=v8:7164 > > Change-Id: I7522ba6ac2bde89c84bcd49bc116a432091a2938 > Reviewed-on: https://chromium-review.googlesource.com/990802 > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Reviewed-by: Clemens Hammacher <clemensh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52343} Bug: v8:7164 Change-Id: Ia883adedf9d54e4a2518d66c85799354d930990e Reviewed-on: https://chromium-review.googlesource.com/996133Reviewed-by:
-
Mythri authored
--cache=code produces and consume cache in different isolates. Earlier we created a new isolate for the run consuming the code cache. This cl changes to create a new isolate when producing the code cache so that RunShell works as expected. Change-Id: I1c73aab2bee429aafdcc52a68ddcf742edfcd652 Reviewed-on: https://chromium-review.googlesource.com/997694 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
-
Vlad Tsyrklevich authored
BUG=v8:7164 Change-Id: I00f5fc6452901538a04315b93550be9bf03a9dd2 Reviewed-on: https://chromium-review.googlesource.com/996406Reviewed-by:
-
Sigurd Schneider authored
This reverts commit 370d95dc. Reason for revert: Unexpected performance regressions 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} TBR=mstarzinger@chromium.org,jarin@chromium.org,sigurds@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:7584 Change-Id: I821d73475d3e62d0e1ee1233d8e18c1f854e26bc Reviewed-on: https://chromium-review.googlesource.com/999413Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#52422}
-
Myles Borins authored
Various fixes necessary to get the script working with V8 6.6 Upstreamed from https://github.com/nodejs/node/pull/19201 Change-Id: Ic7819eb17cf4be8380b8c1811e569236244e7400 Reviewed-on: https://chromium-review.googlesource.com/996858 Commit-Queue: Myles Borins <mborins@google.com> Reviewed-by:
-
Michael Achenbach authored
This reverts commit f9a2e24b. Reason for revert: gc stress failures not all fixed by follow up. Original change's description: > [cleanup] Refactor the Factory > > There is no good reason to have the meat of most objects' initialization > logic in heap.cc, all wrapped by the CALL_HEAP_FUNCTION macro. Instead, > this CL changes the protocol between Heap and Factory to be AllocateRaw, > and all object initialization work after (possibly retried) successful > raw allocation happens in the Factory. > > This saves about 20KB of binary size on x64. > > Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng > Change-Id: Icbfdc4266d7be8b48d2fe085f03411743dc6a0ca > Reviewed-on: https://chromium-review.googlesource.com/959533 > Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Hannes Payer <hpayer@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52416} TBR=jkummerow@chromium.org,yangguo@chromium.org,mstarzinger@chromium.org,hpayer@chromium.org Change-Id: Idbbc53478742f3e9525eee83342afc6aedae122f No-Presubmit: true No-Tree-Checks: true No-Try: true Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Reviewed-on: https://chromium-review.googlesource.com/999414Reviewed-by:
-
Michael Achenbach authored
This reverts commit 8be6842c. Reason for revert: gc stress still broken: https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20GC%20Stress%20-%20custom%20snapshot/builds/18635 https://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20gc%20stress/builds/15893 Original change's description: > Fix GC stress after r52416 > > Allocating elements and/or property backing stores can, due to retrying, > cause a JSObject that has just been allocated in new space to be promoted > to old space, so skipping the write barrier is now an invalid optimization. > > Tbr: hpayer@chromium.org > Change-Id: I4a1eacbd59912dd4aa9069b0636f683fb4674231 > Reviewed-on: https://chromium-review.googlesource.com/998799 > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52417} TBR=jkummerow@chromium.org,hpayer@chromium.org Change-Id: I2c29f34ea8ae950985c1638c21003e1025db06be No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/999512Reviewed-by:
-
Michael Achenbach authored
This reverts commit ad221d14. Reason for revert: Layout test failures: https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/22780 Original change's description: > [wasm] Always enable guard regions on 64-bit platforms > > This change makes full 8 GiB guard regions always enabled on 64-bit > platforms. > > Additionally, since all Wasm memory allocation paths have some form of > guard regions, this removes and simplifies most of the logic around > whether to enable guard regions. > > This is a reland of https://crrev.com/c/985142. > > Bug: v8:7619 > Change-Id: I8bf1f86d6f89fd0bb2144431c7628f15a6b00ba0 > Reviewed-on: https://chromium-review.googlesource.com/996466 > Reviewed-by: Brad Nelson <bradnelson@chromium.org> > Commit-Queue: Eric Holk <eholk@chromium.org> > Cr-Commit-Position: refs/heads/master@{#52412} TBR=bradnelson@chromium.org,eholk@chromium.org Change-Id: Ic15d14c6fa69300bc0fdc036b9fee8ecf65fd397 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7619 Reviewed-on: https://chromium-review.googlesource.com/999412Reviewed-by:
-
Jakob Kummerow authored
Allocating elements and/or property backing stores can, due to retrying, cause a JSObject that has just been allocated in new space to be promoted to old space, so skipping the write barrier is now an invalid optimization. Tbr: hpayer@chromium.org Change-Id: I4a1eacbd59912dd4aa9069b0636f683fb4674231 Reviewed-on: https://chromium-review.googlesource.com/998799Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#52417}
-
Jakob Kummerow authored
There is no good reason to have the meat of most objects' initialization logic in heap.cc, all wrapped by the CALL_HEAP_FUNCTION macro. Instead, this CL changes the protocol between Heap and Factory to be AllocateRaw, and all object initialization work after (possibly retried) successful raw allocation happens in the Factory. This saves about 20KB of binary size on x64. Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: Icbfdc4266d7be8b48d2fe085f03411743dc6a0ca Reviewed-on: https://chromium-review.googlesource.com/959533 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
- 05 Apr, 2018 2 commits
-
-
Camillo Bruni authored
This is another small step towards detaching the JSFunction from Contexts. In order to not break the debugger protocol we need the inferred name on the ScopeInfo chain. This CL might increase memory usage slightly, given that the inferred name field is duplicated on the ScopeInfo. Bug: v8:7066, chromium:818642 Change-Id: I0dd9f18ae69791f774cf835669afa50491f7433b Reviewed-on: https://chromium-review.googlesource.com/995792 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Hannes Payer authored
Bug: chromium:814144 Change-Id: Idd729757608a714921254874af98a4a201340870 Reviewed-on: https://chromium-review.googlesource.com/981146Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#52414}
-
