- 30 Sep, 2018 2 commits
-
-
Shiyu Zhang authored
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}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/e76ff65..79a709e Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/d525ef3..98289bc Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/003e878..7792d28 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I831486cac2077b74f5a4cd89243908dce2cceee4 Reviewed-on: https://chromium-review.googlesource.com/1253186Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#56302}
-
- 29 Sep, 2018 4 commits
-
-
Benedikt Meurer authored
Change the way that the (internal) await closures store the link to the generator object by introducing a dedicated AwaitContext, which stores the generator object into the extension slot (instead of misusing a regular FunctionContext here). Also unify the allocation+initialization of these contexts in the await-related builtins (both for async functions and generators). The rationale behind this is that for (zero-cost) async stack traces, we will need to dig into these contexts and we can do better checking with a dedicated instance type there. As an additional benefit, we save one word per await context, since we just use (the otherwise unused) extension slot to remember the generator object. As yet another benefit we will never accidentally use any of these contexts in the regular scope chain lookups, meaning we can also catch bugs there. And last but not least the objects printing machinery understands these contexts now and can even print the generator object for AwaitContexts for short printing, which is really valuable for debugging. Tbr: ulan@chromium.org Bug: v8:7253, v8:7522, v8:8015 Change-Id: I86955f5701e694e8a10b91ebe5f52705aa90968d Reviewed-on: https://chromium-review.googlesource.com/1249491Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#56301}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/eb7ca76..e76ff65 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/7453eba..d525ef3 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/c5434e9..003e878 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ic48e0bc7b178093fe7a029f466aebd4a9eea9b40 Reviewed-on: https://chromium-review.googlesource.com/1253183 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by:
-
Frank Tang authored
Remove Unpack* methods from all Intl objects Make the icu data in Intl objects more consistent in naming Bug: v8:8248 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: If81a3010265e91919b548dad2dbd11c5ae8e4abd Reviewed-on: https://chromium-review.googlesource.com/1252883Reviewed-by:
-
Frank Tang authored
Bug: v8:7684 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: Ifbdce635d190bd379414d3410aed1208412a9530 Reviewed-on: https://chromium-review.googlesource.com/1251587Reviewed-by:
-
- 28 Sep, 2018 21 commits
-
-
Deepti Gandluri authored
This CL mirrors the ia32 SIMD conversion, Alltrue/AnyTrue operations with minor cleanliness changes to use TempRegisters instead of ScratchRegisters Change-Id: I84d3e148200dd611a72380b24404b75c73c5352d Reviewed-on: https://chromium-review.googlesource.com/1174096 Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#56297}
-
Frank Tang authored
Remove numbering_system and change the type of locale to reduce memory usage of JSDateTimeFormat Bug: v8:8066 Change-Id: I8a319e05312ffa62f22a382bf150bbe9b48f5f54 Reviewed-on: https://chromium-review.googlesource.com/1242093 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
-
Alexey Kozyatinskiy authored
- we can avoid using regexps, - this CL also fixed a bug. R=alph@chromium.org Bug: chromium:870957 Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I9799507b85942be454a7c20d2768fe7442fc965e Reviewed-on: https://chromium-review.googlesource.com/1250403 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by:
Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#56295}
-
Alexey Kozyatinskiy authored
New method was added to console spec [1]. This CL implements it. [1] https://console.spec.whatwg.org/#timelog R=dgozman@chromium.org,yangguo@chromium.org Bug: chromium:854474 Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ie5f249795979bb886cf824ae9f950c5ef78ce04d Reviewed-on: https://chromium-review.googlesource.com/1247641 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#56294}
-
Alexey Kozyatinskiy authored
Sometimes we do not have promise on stack, e.g. Promise.reject call, but we need to attribute this pause with promise rejection. TBR=yangguo@chromium.org Bug: chromium:755728 Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I03ca1e1cd6c21677f0a12ece626e2c8a1938437b Reviewed-on: https://chromium-review.googlesource.com/1249942Reviewed-by:
Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#56293}
-
Georg Neis authored
This is necessary to be able to share the data for read-only objects amongst multiple broker instances. Bug: v8:7790 Change-Id: I0da58f8a9eded06ac6e994bc540a3a1bc481d6a7 Reviewed-on: https://chromium-review.googlesource.com/1251308Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#56292}
-
Mathias Bynens authored
Bug: v8:8015, v8:7467 Change-Id: I0a25fdd7631447235839680c993505179a1cd793 Reviewed-on: https://chromium-review.googlesource.com/1238656Reviewed-by:
-
Michael Achenbach authored
TBR=sergiyb@chromium.org NOTRY=true Bug: chromium:890222 Change-Id: I3c3f8902cc0775edfcdcc85bb0cbc3320bf6c1ef Reviewed-on: https://chromium-review.googlesource.com/1251523 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#56290}
-
Daniel Clifford authored
This CL adds a bit more rigor to the handling of length properties in JSObject-derived classes that explicitly contain that property inline. This involves: - Introducing a new superclass of JSArgumentsObject called JSArgumentsObjectWithLength that is shared with other object instances that also have a fixed length property. - Adding JSArgumentsObjectWithLength to the type hierarchy in Torque, including adding fast-cases for leading the length property for all classes deriving from JSObjectWithLength. - Adding more rigor to Context and NativeContext handling in base.tq. This is useful for the map checks required to verify objects are argument object types derived from JSArgumentsObjectWithLength. Change-Id: I2f0a20601ffcb90b3767cbaeb766e9998d3462ec Reviewed-on: https://chromium-review.googlesource.com/1248661 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#56289}
-
Clemens Hammacher authored
We have the generic {no_reg} and {no_dreg}, other definitions are dead. Currently even {no_dreg} is dead, but I am keeping this because I can see future need for that. R=mstarzinger@chromium.org Bug: v8:8238 Change-Id: I0de597fead6b3def18fd5c530419d3c149f235a8 Reviewed-on: https://chromium-review.googlesource.com/1251123Reviewed-by:Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#56288}
-
Igor Sheludko authored
It was accidentally removed in CL that introduced BoundedPageAllocator. This CL also cleans up the CodeRangeAddressHint a bit. Bug: v8:8096, chromium:887252 Change-Id: Idc84796dd1ff1b440cbe3515732984264defcf2d Reviewed-on: https://chromium-review.googlesource.com/1249125 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#56287}
-
Clemens Hammacher authored
Pending phantom handle callbacks are not reliably executed if the heap shuts down. This can cause to memory leaks or other unwanted behaviour, like in wasm where the NativeModules (held in Managed objects implemented via phantom handles) unregister from the WasmEngine in the second-pass callback. This must be executed before tearing down the WasmEngine. This CL fixes this by running pending callback synchronously on heap tear down. R=ulan@chromium.org, mlippautz@chromium.org Bug: v8:8208 Change-Id: I27b630c4d8f1fb12309040ea2179b64eed38710a Reviewed-on: https://chromium-review.googlesource.com/1249101 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
Minor refactoring, for readability and performance. R=ahaas@chromium.org Bug: v8:8015 Change-Id: I30c4a76998c8867aea0e08fd982b4425d4ae8fef Reviewed-on: https://chromium-review.googlesource.com/1251163Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#56285}
-
Igor Sheludko authored
Trimming may free up some allocatable pages that can be reused by subsequent allocations. This CL also fixes base::AddressRegion::contains(Address, size_t). Bug: v8:8096 Change-Id: I3b7381fd32f7dbf186dffc1a26d5a88cd8a30d2f Reviewed-on: https://chromium-review.googlesource.com/1249127Reviewed-by:
-
Toon Verwaest authored
|this| cannot be an ambiguous declaration. Actual declarations are inserted upon function scope creation, so we can simply parse as reference and it will resolve correctly. Change-Id: I3aaa1a2666b4caffbf8524caec7068125e10240b Reviewed-on: https://chromium-review.googlesource.com/1251162Reviewed-by:
Marja Hölttä <marja@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#56283}
-
Clemens Hammacher authored
This reverts commit e4c650ad. Reason for revert: Break Linux nosnap: https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Linux%20-%20nosnap%20-%20debug/20786 Original change's description: > [heap] Free dead young generation large objects. > > Bug: chromium:852420 > Change-Id: I77479c3a96bcae6041ddce316c5062f129447edd > Reviewed-on: https://chromium-review.googlesource.com/1249124 > Commit-Queue: Hannes Payer <hpayer@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#56280} TBR=hpayer@chromium.org,mlippautz@chromium.org Change-Id: If35a09497e09f5cc7ceef8ec33a7c86761f2a336 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:852420 Reviewed-on: https://chromium-review.googlesource.com/1251124Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#56282}
-
Florian Sattler authored
PreParser now does not longer track which kind of error occurred. If we see an error we reparse with the parser and report the error. Furthermore, this fixes tests in test-parsing. Change-Id: I1860949fab4d65ff4a5a1b63796c7574494f9d50 Reviewed-on: https://chromium-review.googlesource.com/1231173 Commit-Queue: Florian Sattler <sattlerf@google.com> Reviewed-by:
Adam Klein <adamk@chromium.org> Reviewed-by:
-
Hannes Payer authored
Bug: chromium:852420 Change-Id: I77479c3a96bcae6041ddce316c5062f129447edd Reviewed-on: https://chromium-review.googlesource.com/1249124 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
-
Jaroslav Sevcik authored
Bug: chromium:890057 Change-Id: I98bc278ebc202c3d8f6417367bd1c592e4824011 Reviewed-on: https://chromium-review.googlesource.com/1250481 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#56279}
-
Alexey Kozyatinskiy authored
We might have empty frame_inspector_ here, let's fast return in this case. R=yangguo@chromium.org Bug: chromium:864920 Change-Id: Ia8012251877bb4e04b7f756db72a3039bca6fa9c Reviewed-on: https://chromium-review.googlesource.com/1250408Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/343caac..eb7ca76 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/3cf15a9..7453eba Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/f221bac..95d4c85 Rolling v8/third_party/fuchsia-sdk: https://chromium.googlesource.com/chromium/src/third_party/fuchsia-sdk/+log/ce131de..ff74025 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/86c7e6d..c5434e9 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I7aa1be4f55e02ae0c4df27ccabb77940fbf8f4d3 Reviewed-on: https://chromium-review.googlesource.com/1249960Reviewed-by:
-
- 27 Sep, 2018 13 commits
-
-
Benedikt Meurer authored
The Parser inserts a temporary .promise variable to hold the outer promise for async functions, but doesn't assign an actually visible name to it. This change puts the name ".promise" on it (similar to what we do for other special variables like .result), which makes it easier to debug this (for V8 developers). It's not observable to regular developers. Bug: v8:7522, v8:8015 Change-Id: I388352ad931a49102cb5afe350314337a505a150 Reviewed-on: https://chromium-review.googlesource.com/1249106Reviewed-by:
-
Vasili Skurydzin authored
Bug: v8:8193 GCC bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61976 Change-Id: I0d4efca4da03ef82651325e15ddf2160022bc8de Reviewed-on: https://chromium-review.googlesource.com/1228633Reviewed-by:
Daniel Clifford <danno@chromium.org> Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#56275}
-
Vasili Skurydzin authored
test/cctest/compiler/value-helper.h: fix due to a GCC bug affecting padding of aggregate data types on Aix. GCC bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61976 Change-Id: I303b09a9a84b372033c16cbf157d5fc2bf25f93a Reviewed-on: https://chromium-review.googlesource.com/1244616Reviewed-by:
-
Junliang Yan authored
on ppc64/s390x, gcc 6.3 complains "error: unknown option after '#pragma GCC diagnostic' kind". This is to avoid using the option on these platforms. R=jkummerow@chromium.org Bug: v8:8100 Change-Id: I61e5b70038c41cb62889a36694ffcc36fa6deee9 Reviewed-on: https://chromium-review.googlesource.com/1246803Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#56273}
-
Toon Verwaest authored
For statementlists we only need to track whether they are null or not. We especially do not need to track possible variable declarations. Change-Id: I66377521c924931a1871e5df0e55a7b45f169155 Reviewed-on: https://chromium-review.googlesource.com/1249267Reviewed-by:
-
Yang Guo authored
R=petermarshall@chromium.org Bug: chromium:680662 Change-Id: If48d1043dbe1e1bb695ec890c23e103a6cacf2d4 Reviewed-on: https://chromium-review.googlesource.com/1244220 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#56271}
-
Ivica Bogosavljevic authored
Port c2088790 Change-Id: Ia57a3a47bbc6f99fdf40ea58d01cbb007b4409e3 Reviewed-on: https://chromium-review.googlesource.com/1245773Reviewed-by:
Sreten Kovacevic <skovacevic@wavecomp.com> Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Sreten Kovacevic <skovacevic@wavecomp.com> Cr-Commit-Position: refs/heads/master@{#56270}
-
Hannes Payer authored
Bug: v8:8228 Change-Id: I5a666d3bfebe4bce9e06cc6a7fd82aac1fbf2a61 Reviewed-on: https://chromium-review.googlesource.com/1249144Reviewed-by:
-
Michael Achenbach authored
TBR=santa Change-Id: Id26ecc661066d8ec11df5375f5cf40bc89e0cc62 Reviewed-on: https://chromium-review.googlesource.com/1249266Reviewed-by:
-
Florian Sattler authored
Change-Id: I49a4e9740f6a3715ca5cdafd121b3b99fed8dc6b Reviewed-on: https://chromium-review.googlesource.com/1245428Reviewed-by:
-
Creddy authored
This is a reland of eccf1867 Original change's description: > [interpreter] Separate bytecodes for one-shot property loads and stores > > Create LdaNamedPropertyNoFeedback and StaNamedPropertyNoFeedback > for one-shot property loads and stores. This CL replaces the runtime > calls with new bytecodes for named property load stores in one-shot code. > the runtime calls needed extra set of consecutive registers and > additional move instructions. This increased the size of > bytecode-array and possibly extended the life time of objects. > By replacing them with NoFeedback bytecodes we avoid these issues. > > Bug: v8:8072 > Change-Id: I20a38a5ce9940026171d870d354787fe0b7c5a6f > Reviewed-on: https://chromium-review.googlesource.com/1196725 > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Reviewed-by: Georg Neis <neis@chromium.org> > Commit-Queue: Chandan Reddy <chandanreddy@google.com> > Cr-Commit-Position: refs/heads/master@{#56211} Bug: v8:8072 Change-Id: Ie8e52b37daf35c7bc08bb910d7b15a9b783354e4 Reviewed-on: https://chromium-review.googlesource.com/1245742 Commit-Queue: Chandan Reddy <chandanreddy@google.com> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Toon Verwaest authored
Change-Id: Ia5f8ff6279860db83e5bb95206d3e740a13fcc3c Reviewed-on: https://chromium-review.googlesource.com/1248621Reviewed-by:
-
Peter Marshall authored
This reverts commit 5fb55097. Reason for revert: This does not make sense for the chromium use-case Original change's description: > [API] Change GetCodeRange to match the style of GetEmbeddedCodeRange > > Deprecate GetCodeRange(void** start, size_t* length_in_bytes) in favor > of a new signature MemoryRange GetCodeRange() which is consistent with > that of GetEmbeddedCodeRange. > > Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng > Change-Id: Ic5e244981422a2c75485c851ca768e54914cc539 > Reviewed-on: https://chromium-review.googlesource.com/1245741 > Reviewed-by: Yang Guo <yangguo@chromium.org> > Commit-Queue: Peter Marshall <petermarshall@chromium.org> > Cr-Commit-Position: refs/heads/master@{#56241} TBR=yangguo@chromium.org,petermarshall@chromium.org Change-Id: I51e8bedcb099d3f153ead1451284bf97017bedcf No-Presubmit: true No-Tree-Checks: true No-Try: true Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Reviewed-on: https://chromium-review.googlesource.com/1249126Reviewed-by:
-
