- 02 Oct, 2019 9 commits
-
-
Jakob Kummerow authored
The creator of the allocator retains ownership and is responsible for its eventual destruction. Change-Id: Iaf1b24bee7153b3b1a75df99974adff42c6a197f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1835545 Auto-Submit: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#64084}
-
Michael Lippautz authored
Fix corner case where we would try to read a property when having a pending or scheduled exception. Re-add tests. Bug: chromium:1006640 Change-Id: I2fc84ee0f6145db2d200a8b9abf57fdc4b12a5a3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1835531Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#64083}
-
Mythri A authored
This is a reland of 9efe315e after marking box2d slow. Original change's description: > Mark functions for optimization only on bytecode budget interrupts > > We used to mark functions for optimization on any interrupt. This sometimes > causes functions to OSR when not needed. The implementation was such because > we didn't have a different runtime function to distinguish bytecode budget > interrupts from other interrupts. For lazy feedback allocation we added a > new runtime function for bytecode budget interrupts so it makes it easier > to actually mark functions only when needed. > > This also includes a fix to reduce the stack limits for interrupts when > entering a scope that allows interrupts from a postponed interrupt scope. > > Bug: chromium:993061 > Change-Id: Iaf7b4dccb7a503e5b6bfcbb993bc7482aa593955 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829218 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Commit-Queue: Mythri Alle <mythria@chromium.org> > Cr-Commit-Position: refs/heads/master@{#64048} Bug: chromium:993061 Change-Id: I24dae03357d6c368e4173db3f071e8ab09e9d6dc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832173Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#64082}
-
Georg Neis authored
... in order to print more information when it's disabled. Bug: v8:7790 Change-Id: I58a5dacbbe9551814e62b157885c83001924a59b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1835534 Auto-Submit: Georg Neis <neis@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#64081}
-
Jakob Gruber authored
The natives blob is deprecated and will be removed in the next release. This commit does two things, 1. it disables the v8_extra_library_files gn argument which will make building natives_blob.bin through gn impossible; 2. it marks API functions associated with the natives blob as V8_DEPRECATE_SOON. Embedders should remove any uses of SetNativesDataBlob and replace all calls to InitializeExternalStartupData(const char*, const char*) with the new function InitializeExternalStartupDataFromFile(const char*) Step 2 is to mark API functions as V8_DEPRECATED. Step 3, in the next V8 release, is to remove these functions and all other natives support in V8. Bug: v8:7624 Change-Id: I745e96c60204a9b94d9240be65dd59bb9bdd0699 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1824944 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
GC stress flags (--gc-interval, --random-gc-interval) could trigger unexpected fake allocation failures while trying to fill up a page. An AlwaysAllocateScope suppresses that. Drive-by fix: allocation requests with exactly kMaxRegularHeapObjectSize can take the fast path. Bug: v8:9700 Change-Id: I7fa35e56848e74f12d3606da453e1ae7254c268b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1834121Reviewed-by:
-
Clemens Backes authored
We need to register the unwind info for each code space (it was just done for the first one). Otherwise we fail when freeing the native module, where we try to unregister the unwind info again for each code space. This CL moves the call to {RegisterNonABICompliantCodeRange} from {NewNativeModule} to {AddCodeSpace}, so it happens whenever a new code space is added. R=jgruber@chromium.org CC=paolosev@microsoft.com Bug: chromium:1008597, v8:9477, v8:9795 Change-Id: I20121b2a2fde4d37432dd7e13b19cdf99129e6a4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832178 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by:Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#64078}
-
Michael Lippautz authored
Bug: chromium:1006640 Change-Id: I0f38ed9c44b6a2a6cfd52fdd9e177768f57beb11 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1833692 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/69e3270..5de2214 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/5f4659d..16236fc Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/a19d353..5eac9d3 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: I45412c50e72c4899b4e88046a9e2565f07cdad5e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1833873Reviewed-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@{#64076}
-
- 01 Oct, 2019 22 commits
-
-
Igor Sheludko authored
... by flipping the flag. Bug: v8:9706 Change-Id: Ie0e70a243a5a6a703cdaa27c1ed55a78d9904bbe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1826732 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#64075}
-
Jaime Bernardo authored
Explicitly #include<string> in v8.h, since std::string is referenced in it. In the C++ STL shipped with Visual Studio 2019, none of the headers included in v8.h ends up including the C++ string header, which caused a compile error. Bug: v8:9793 Change-Id: I84a133dd10dd6dcc7b70287af393e82cf0dc97df Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1834321Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#64074}
-
Ng Zhi An authored
Bug: v8:9728 Change-Id: Ic15d793e6408af1ea2e1f7f71b9130300d359a95 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1808417Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#64073}
-
Ross McIlroy authored
TurboProp will not reschedule after effect-control linearization, so the graph-assembler will be used to modify the schedule as new nodes are added. To enable this, ensure we use the graph assembler for all node creation from effect-control linearization onwards. BUG=v8:9684 Change-Id: I2be3f5d2a3f2cbee44c72bb397e9bd1d9ac7de05 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832166 Auto-Submit: Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#64072}
-
Ng Zhi An authored
Change-Id: I5dcc3f708ca05a0d3b504cb4d7a89693ca0717b4 Bug: v8:9396 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1819521Reviewed-by:
-
Frank Tang authored
* Throws RangeError only when the calendar and numberingSystem is ill-formed. * Set the calendar and numberingSystem to the locale only if the values are valid. * Fix the order of GetOption of "localeMatcher". * Add more unit tests. See https://github.com/tc39/ecma402/pull/175 for details. Bug: v8:9786, v8:9787, v8:9788 Change-Id: Ic0f918ad7d9afb0b7c8df39caa0f44ef07ca10c0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1830345 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#64070}
-
Frank Tang authored
Bug: v8:9155 Change-Id: I54c65ee28171064f596fc305bb718613640f251a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832636Reviewed-by:
-
Joshua Litt authored
Removes the static protector values from isolate now that they are no longer needed. This is the final cl in the migration effort. Bug: v8:9463 Change-Id: I2127ef6c8a0cdaf0ccf28aed12539335ef985704 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1827455Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
Igor Sheludko authored
Bug: v8:9706 Change-Id: I5779e2fbaec5741cc9b8d44f7f3f721400e70b28 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832174 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Dan Elphick authored
Pushes the optimised code path to after the main interpreter path, so the straightline path is just normal interpretation. Bug: v8:9771 Change-Id: I2f48ff290efcd85a5e30cf823027919560f8a56a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829220Reviewed-by:
-
Peter Marshall authored
This was missed when changing Object to hold a ptr field instead of abusing the this pointer. This was printing the stack address of the particular Object rather than the location of the printed code object on the heap. Change-Id: I5c884464419debcbc70b73fe8bdfa8107f2bdb71 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1833681 Auto-Submit: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
-
Jakob Gruber authored
This is a reland of 66129430 Fixed: Unaligned reads, unspecified evaluation order. Original change's description: > [regexp] Bytecode peephole optimization > > Bytecodes used by the regular expression interpreter often occur in > specific sequences. The number of dispatches in the interpreter can be > reduced if those sequences are combined into a single bytecode. > > This CL adds a peephole optimization pass for regexp bytecodes. > This pass checks the generated bytecode for pre-defined sequences that > can be merged into a single bytecode. > > With the currently implemented bytecode sequences a speedup of 1.12x on > regex-dna and octane-regexp is achieved. > > Bug: v8:9330 > Change-Id: I827f93273a5848e5963c7e3329daeb898995d151 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1813743 > Commit-Queue: Patrick Thier <pthier@google.com> > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63992} Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng Cq-Include-Trybots: luci.v8.try:v8_linux_gcc_rel Bug: v8:9330,chromium:1008502,chromium:1008631 Change-Id: Ib9fc395b6809aa1debdb54d9fba5b7f09a235e5b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1828917Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
-
Ana Peško authored
This is a reland of cfb60d43 Original change's description: > [regexp] Eagerly tier-up for very long strings > > For very long subject strings, the regexp interpreter is currently much slower > than the native machine code execution. This CL implements eager tier-up to the > compiler to avoid the performance penalty for subject strings of length greater > than 1000. > > Change-Id: I244ccbd60255e0f3bedc493b1cc3d25cdd42133e > Bug: v8:9566 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829273 > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Commit-Queue: Ana Pesko <anapesko@google.com> > Cr-Commit-Position: refs/heads/master@{#64046} Bug: v8:9566 Change-Id: I81a10728c64ce3b35258c31eb8178e458d3de205 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832167Reviewed-by:
-
Georg Neis authored
This is an experiment to see the memory/performance impact. Bug: v8:9775 Change-Id: I2ae61ae8bb5c6c1c55436e96c4b2d8201cbf4739 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832177Reviewed-by:
-
chrome://traceMike Stanton authored
Bug: chromium:1005195 Change-Id: I41b8526d1394d82b06bab975dc0cc18c080dfd60 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829271 Commit-Queue: Michael Stanton <mvstanton@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#64061}
-
Leszek Swirski authored
Change-Id: I822f3961b2ec5ef8fb7ca4765cb7c9fd38514223 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832171 Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#64060}
-
Leszek Swirski authored
Avoid emitting deprecation checks for these fields. Bug: v8:9606 Change-Id: Id3e317a8c36728b3c7b063743ef9d36aa1209176 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832170 Commit-Queue: Igor Sheludko <ishell@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
David Carlier authored
Change-Id: I4d4c6e8a6371102ae7b2ece7cbbc068cdd8c6799 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832165Reviewed-by:
Clemens Backes <clemensb@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#64058}
-
Dan Elphick authored
Moves CodeStubAssembler::BranchIfPrototypesHaveNoElements to AccessorAssembler and TNodifies it on the way. Bug: v8:9396 Change-Id: Ie5d8ad5abc3dbdb688c0cbee4610cd441ba1a9b1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1826736 Auto-Submit: Dan Elphick <delphick@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Reviewed-by:
-
Andreas Haas authored
Apparently this is necessary. R=ulan@chromium.org Bug: v8:9396 Change-Id: Ia7c439308fb7edbb901f595aeb9fbf9389858daa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832161Reviewed-by:
-
Michael Achenbach authored
It was confusing to silently run test262 only in the default variant with a switch on the infra side. We'll remove that switch in a follow up and explicitly configure the testing variant for test262 in builders.pyl. Bug: v8:9791 Change-Id: I0da351ff981c833704f51a415225aff24df1664a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829269Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#64055}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/0a96846..69e3270 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/0081c0f..a19d353 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: Ie36db05802205713ad5a49cfa180c58e32fda94f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1831187Reviewed-by:
-
- 30 Sep, 2019 9 commits
-
-
Francis McCabe authored
This reverts commit 9efe315e. Reason for revert: Causing time out issues on box2d tests: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux%20-%20debug/27752 and https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20-%20debug/29630 Original change's description: > Mark functions for optimization only on bytecode budget interrupts > > We used to mark functions for optimization on any interrupt. This sometimes > causes functions to OSR when not needed. The implementation was such because > we didn't have a different runtime function to distinguish bytecode budget > interrupts from other interrupts. For lazy feedback allocation we added a > new runtime function for bytecode budget interrupts so it makes it easier > to actually mark functions only when needed. > > This also includes a fix to reduce the stack limits for interrupts when > entering a scope that allows interrupts from a postponed interrupt scope. > > Bug: chromium:993061 > Change-Id: Iaf7b4dccb7a503e5b6bfcbb993bc7482aa593955 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829218 > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Commit-Queue: Mythri Alle <mythria@chromium.org> > Cr-Commit-Position: refs/heads/master@{#64048} TBR=rmcilroy@chromium.org,mythria@chromium.org,leszeks@chromium.org Change-Id: I97938934fdaa030b958695d18e1788d75c17077c No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:993061 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832645Reviewed-by:
Francis McCabe <fgm@chromium.org> Commit-Queue: Francis McCabe <fgm@chromium.org> Cr-Commit-Position: refs/heads/master@{#64053}
-
Suraj Sharma authored
Since slow handler was previously not a Smi. The DCHECK assumed any Smi Handler on this path should be a proxy handler. Now it Checks for both, and should continue if the current handler is a slow handler. Bug: chromium:1008632 Change-Id: I079960894d7320d8d658d0990e8c32db51703206 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1828480Reviewed-by:
-
Vasili Skurydzin authored
prepare for ptr compression Change-Id: Ia459ad18a30fbfd8e51bd99735f0d63644d30b8f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1831788Reviewed-by:
Joran Siu <joransiu@ca.ibm.com> Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#64051}
-
Clemens Backes [né Hammacher] authored
This reverts commit 35ca0abd. Reason for revert: Speculative revert for https://crbug.com/1008597. Original change's description: > [wasm] Ship far jump tables > > This flips the --wasm-far-jump-table flag. It will allow for more than > 128MB of code space per wasm module on arm64, and will increase the > limit on the number of modules per process on x64 (was ~1000 before, > because we reserved 1GB for the code space per module). > > R=mstarzinger@chromium.org > > Bug: v8:9477 > Change-Id: I870ec616f4812e38ef1e3fccf0629854a247bb4f > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815247 > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Clemens Backes [né Hammacher] <clemensh@chromium.org> > Cr-Commit-Position: refs/heads/master@{#63967} TBR=mstarzinger@chromium.org,clemensb@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: v8:9477, chromium:1008597 Change-Id: Ie8740e09925130b304a37d97904443026aabae85 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832162Reviewed-by:
-
Z Nguyen-Huu authored
Bug: v8:9781 Change-Id: I1f82a828f103cc2aa3f9553214f6b4867ffc3b17 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829897 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
-
Mythri A authored
We used to mark functions for optimization on any interrupt. This sometimes causes functions to OSR when not needed. The implementation was such because we didn't have a different runtime function to distinguish bytecode budget interrupts from other interrupts. For lazy feedback allocation we added a new runtime function for bytecode budget interrupts so it makes it easier to actually mark functions only when needed. This also includes a fix to reduce the stack limits for interrupts when entering a scope that allows interrupts from a postponed interrupt scope. Bug: chromium:993061 Change-Id: Iaf7b4dccb7a503e5b6bfcbb993bc7482aa593955 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829218Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Ana Pesko authored
This reverts commit cfb60d43. Reason for revert: Several bots timing out, e.g. https://ci.chromium.org/p/v8/builders/ci/V8%20Linux%20-%20gc%20stress/24717 Original change's description: > [regexp] Eagerly tier-up for very long strings > > For very long subject strings, the regexp interpreter is currently much slower > than the native machine code execution. This CL implements eager tier-up to the > compiler to avoid the performance penalty for subject strings of length greater > than 1000. > > Change-Id: I244ccbd60255e0f3bedc493b1cc3d25cdd42133e > Bug: v8:9566 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829273 > Reviewed-by: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Yang Guo <yangguo@chromium.org> > Commit-Queue: Ana Pesko <anapesko@google.com> > Cr-Commit-Position: refs/heads/master@{#64046} TBR=yangguo@chromium.org,petermarshall@chromium.org,anapesko@google.com TBR=yangguo@chromium.org Change-Id: Id8dd362617988c8c5efa87ae157ee91c96cb1fdf No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9566 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832163Reviewed-by:
-
Ana Peško authored
For very long subject strings, the regexp interpreter is currently much slower than the native machine code execution. This CL implements eager tier-up to the compiler to avoid the performance penalty for subject strings of length greater than 1000. Change-Id: I244ccbd60255e0f3bedc493b1cc3d25cdd42133e Bug: v8:9566 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829273Reviewed-by:
-
Milad Farazmand authored
Port 1e4bb087 Original Commit Message: x64 code path is different and we can't do this optimization. R=solanes@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I173d7339706a9c09d3e6519d1cee36fa15692aca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1829171 Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Reviewed-by:
-
