{"push_id":950560729,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"8f0fd8c0370ae8c5aab56491b879d7e30c329062","before":"4cbd63c9bfee2b734f67f5bd36b98dcab072021f","commits":[{"sha":"e2e7dc32eff65c727a7f5e1cae45db0f83607c04","author":{"email":"c942d126fed7cdf21e2306e20ba5eaf628ad30de@chromium.org","name":"mvstanton"},"message":"Revert of Type Feedback Vector lives in the closure (patchset #12 id:260001 of https://codereview.chromium.org/1563213002/ )\n\nReason for revert:\nFAilure on win32 bot, need to investigate webkit failures.\n\nOriginal issue's description:\n> Type Feedback Vector lives in the closure\n>\n> We get less \"pollution\" of type feedback if we have one vector per native\n> context, rather than one for the whole system. This CL moves the vector\n> appropriately.\n>\n> We rely more heavily on the Optimized Code Map in the SharedFunctionInfo. The\n> vector actually lives in the first slot of the literals array (indeed there is\n> great commonality between those arrays, they can be thought of as the same\n> thing). So we make greater effort to ensure there is a valid literals array\n> after compilation.\n>\n> This meant, for performance reasons, that we needed to extend\n> FastNewClosureStub to support creating closures with literals. And ultimately,\n> it drove us to move the optimized code map lookup out of FastNewClosureStub\n> and into the compile lazy builtin.\n>\n> The heap change is trivial so I TBR Hannes for it...\n>\n> TBR=hpayer@chromium.org\n>\n> BUG=\n>\n> Committed: https://crrev.com/a5200f7ed4d11c6b882fa667da7a1864226544b4\n> Cr-Commit-Position: refs/heads/master@{#33518}\n\nTBR=bmeurer@chromium.org,akos.palfi@imgtec.com\n# Skipping CQ checks because original CL landed less than 1 days ago.\nNOPRESUBMIT=true\nNOTREECHECKS=true\nNOTRY=true\nBUG=\n\nReview URL: https://codereview.chromium.org/1632993003\n\nCr-Commit-Position: refs/heads/master@{#33520}","distinct":true,"url":"https://api.github.com/repos/paul99/v8mips/commits/e2e7dc32eff65c727a7f5e1cae45db0f83607c04"},{"sha":"cfaeb63b6825ef87e499b0c7beb09b475dcf5acc","author":{"email":"99ad26d4d7419a5a7143fa062693d7292b2303a2@chromium.org","name":"jarin"},"message":"Replace HeapType with a non-templated FieldType class.\n\nThis replace HeapType with a dedicated class that implements just what we need for field type tracking. In the next CL, I plan to remove FieldType::Iterator because FieldType can iterate over at most one map.\n\nThe ultimate plan is to get rid of templates in types.(h|cc) and remove type-inl.h.\n\nTBR=rossberg@chromium.org\n\nReview URL: https://codereview.chromium.org/1636013002\n\nCr-Commit-Position: refs/heads/master@{#33521}","distinct":true,"url":"https://api.github.com/repos/paul99/v8mips/commits/cfaeb63b6825ef87e499b0c7beb09b475dcf5acc"},{"sha":"8349ee0c269d527d1d1c6f11a685ee4ee221720d","author":{"email":"1cf0af8245a3a17a632a2c73531392b0f9761c76@chromium.org","name":"yangguo"},"message":"[debugger] muting break positions should work for the entire statement.\n\nA statement could have several break positions. The entire statement\nshould be considered muted if break points across all these break\npositions evaluate to false.\n\nR=verwaest@chromium.org\nBUG=chromium:429167\nLOG=N\n\nReview URL: https://codereview.chromium.org/1615903002\n\nCr-Commit-Position: refs/heads/master@{#33522}","distinct":true,"url":"https://api.github.com/repos/paul99/v8mips/commits/8349ee0c269d527d1d1c6f11a685ee4ee221720d"},{"sha":"8f0fd8c0370ae8c5aab56491b879d7e30c329062","author":{"email":"366b911b1713540eac38e45e389ba1ab59b56004@chromium.org","name":"mlippautz"},"message":"[heap] Parallel newspace evacuation, semispace copy, and compaction \\o/\n\nAll parallelism can be turned off using --predictable, or --noparallel-compaction.\n\nThis patch completely parallelizes\n - semispace copy: from space -> to space (within newspace)\n - newspace evacuation: newspace -> oldspace\n - oldspace compaction: oldspace -> oldspace\n\nPreviously newspace has been handled sequentially (semispace copy, newspace\nevacuation) before compacting oldspace in parallel. However, on a high level\nthere are no dependencies between those two actions, hence we parallelize them\naltogether. We base the number of evacuation tasks on the overall set of\nto-be-processed pages (newspace + oldspace compaction pages).\n\nSome low-level details:\n - The hard cap on number of tasks has been lifted\n - We cache store buffer entries locally before merging them back into the global\n   StoreBuffer in a finalization phase.\n - We cache AllocationSite operations locally before merging them back into the\n   global pretenuring storage in a finalization phase.\n - AllocationSite might be compacted while they would be needed for newspace\n   evacuation. To mitigate any problems we defer checking allocation sites for\n   newspace till merging locally buffered data.\n\nCQ_EXTRA_TRYBOTS=tryserver.v8:v8_linux_arm64_gc_stress_dbg,v8_linux_gc_stress_dbg,v8_mac_gc_stress_dbg,v8_linux64_asan_rel,v8_linux64_tsan_rel,v8_mac64_asan_rel\nBUG=chromium:524425\nLOG=N\nR=hpayer@chromium.org, ulan@chromium.org\n\nReview URL: https://codereview.chromium.org/1577853007\n\nCr-Commit-Position: refs/heads/master@{#33523}","distinct":true,"url":"https://api.github.com/repos/paul99/v8mips/commits/8f0fd8c0370ae8c5aab56491b879d7e30c329062"}]}