- 12 Nov, 2018 28 commits
-
-
Jakob Kummerow authored
Bug: v8:3770 Change-Id: I413ce57f7fa91cef2445995ca22650477f92b0df Reviewed-on: https://chromium-review.googlesource.com/c/1321892Reviewed-by:
Dan Elphick <delphick@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#57445}
-
Frank Tang authored
Bug: v8:8424 Change-Id: Ic4f5b229dca4c3a802701aaa6e2093e280739a78 Reviewed-on: https://chromium-review.googlesource.com/c/1328646Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#57444}
-
Junliang Yan authored
R=joransiu@ca.ibm.com Change-Id: I09f57abe9a0fdd8d42c9f52b745a0f9957b67e58 Reviewed-on: https://chromium-review.googlesource.com/c/1330264Reviewed-by:
Joran Siu <joransiu@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#57443}
-
Sathya Gunasekaran authored
Bug: v8:6443, v8:7569 Change-Id: Ie1733198af76d07ac4601c5058af531701434fef Reviewed-on: https://chromium-review.googlesource.com/c/1331549Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#57442}
-
Clemens Hammacher authored
R=gdeepti@chromium.org Change-Id: I8fabe18101b7e23b5e2971fedd0bd3591783dc85 Reviewed-on: https://chromium-review.googlesource.com/c/1329699Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57441}
-
Sathya Gunasekaran authored
Bug: v8:6443, v8:7569 Change-Id: Ia7f0550500b19e93d78983db2e20d020bc0ff164 Reviewed-on: https://chromium-review.googlesource.com/c/1329700Reviewed-by:
-
Sathya Gunasekaran authored
in SmallOrderedHashTable Bug: v8:6443, v8:7569 Change-Id: I14572b1acc30df45d0554ee7e8e129da85791529 Reviewed-on: https://chromium-review.googlesource.com/c/1329698Reviewed-by:
-
Sathya Gunasekaran authored
Bug: v8:6443, v8:7569 Change-Id: Iee039eddd07a7bbc38c8e9f7deca00d5183e702a Reviewed-on: https://chromium-review.googlesource.com/c/1329697Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#57438}
-
Ben L. Titzer authored
This CL splits the backend of TurboFan off into its own directory, without changing namespaces. This makes ownership management a bit more fine-grained with a logical separation. R=mstarzinger@chromium.org,jarin@chromium.org,adamk@chromium.org Change-Id: I2ac40d6ca2c4f04b8474b630aae0286ecf79ef42 Reviewed-on: https://chromium-review.googlesource.com/c/1308333 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
1) For the code space estimate, exclude everything except code. 2) Add some static code size per function. 3) Add some static code size per module. 4) Include signature zone memory. R=mstarzinger@chromium.org Change-Id: Ifa9ac347edf98c2e63ab3201a64ac2e0a3de28e5 Reviewed-on: https://chromium-review.googlesource.com/c/1118263Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57436}
-
Clemens Hammacher authored
After the first decoder error, the streaming processor should not be called again. To enforce this, reset the {processor_} field. This also makes the {ok_} field redundant. Note that this refactoring is also necessary for a future CL which makes the {StreamingProcessor} keep the {AsyncCompileJob} alive. By resetting the processor, we also remove that link. R=ahaas@chromium.org Bug: v8:7921 Change-Id: I42f5ed26a8f26c3dc8db5676557a0d82021e132e Reviewed-on: https://chromium-review.googlesource.com/c/1329179 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#57435}
-
Jakob Gruber authored
This removes unused code (macros.py, runtime functions). As IS_VAR is now unused we can remove support from the parser. Bug: v8:7624 Change-Id: Ia1c5e23f4c2caa85310d3f9a557218fc52d200f2 Reviewed-on: https://chromium-review.googlesource.com/c/1329696Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Igor Sheludko authored
Bug: v8:8182 Change-Id: I9c83428b54764db99e83a6bf6ef556b68fd546b0 Reviewed-on: https://chromium-review.googlesource.com/c/1329694Reviewed-by:
-
Sathya Gunasekaran authored
... to OrderedNameDict Bug: v8:6443, v8:7569 Change-Id: Ic952c88e3256935391707032320913069020b045 Reviewed-on: https://chromium-review.googlesource.com/c/1329682Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#57432}
-
Sathya Gunasekaran authored
Specialize FindEntry for OrderedNameDictionary Bug: v8:6443, v8:7569 Change-Id: I776415fde6bc2ea292b645fbca6952c7bb09d89d Reviewed-on: https://chromium-review.googlesource.com/c/1329962Reviewed-by:
-
Sathya Gunasekaran authored
This is the larger dictionary specialized for Name. To be used as a property backing store. More methods and tests will be added in the future as it reaches parity with NameDictionary. Bug: v8:6443, v8:7569 Change-Id: I8f5d88b2f6f4e14d4851548566ffa9f59535358b Reviewed-on: https://chromium-review.googlesource.com/c/1329204Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
I just ran into this when creating a test case. The huge spread caused a RangeError (stack overflow). It's not causing problems for the tests we currently have, but let's fix it anyway. R=ahaas@chromium.org Change-Id: Ib67f059f2981ccc6239ba4ae05611e20eb3aa191 Reviewed-on: https://chromium-review.googlesource.com/c/1329177 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
Fixes building in MSVS with -std:c++17 Refs: https://en.cppreference.com/w/cpp/utility/functional/unary_function Change-Id: Ibb05b6810cae029aae33957f3eb52cc3a9e4863e Reviewed-on: https://chromium-review.googlesource.com/c/1227322 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#57428}
-
Toon Verwaest authored
Now that identifiers in the preparser also carry their string, we can simply check that rather than relying on a weird "keyword". Dropping __proto__ as a keyword allows us to delist '_' as keyword character. Change-Id: I775df25f77a84de92a60790ca665f16d52abf4bf Reviewed-on: https://chromium-review.googlesource.com/c/1329692 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
gcc 4.8 fails to compile an {std::atomic::compare_exchange_strong} with {memory_order_acq_rel} with this error: error: invalid failure memory model for ‘__atomic_compare_exchange’ This makes our gcov bot fail: https://ci.chromium.org/p/v8/builders/luci.v8.ci/V8%20Linux64%20-%20gcov%20coverage/16053 According to the documentation, giving a single {memory_order_acq_rel} is equivalent to specifying {memory_order_acq_rel} as success memory order and {memory_order_acquire} for failure. This CL refactors the code to do this explicitly. R=ulan@chromium.org CC=machenbach@chromium.org Bug: v8:8238 Cq-Include-Trybots: luci.v8.try:v8_linux64_tsan_rel Change-Id: Idcc69ee4b4ac53edc4fd1aa28eac7377f08044ce Reviewed-on: https://chromium-review.googlesource.com/c/1329693Reviewed-by: -
Daniel Clifford authored
Change-Id: Ie7f3cec3ae6541f46b3f43c83bd9d53de7614d20 Reviewed-on: https://chromium-review.googlesource.com/c/1329689 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by:
-
Toon Verwaest authored
Now that we have no more do-expressions, we don't need to reparent variables and declarations anymore. However, it's still possible that temporaries were implicitly allocated. We still need to move those. Bug: chromium:904255 Change-Id: Ia8a90eb822b9db123ffb0bad58e4b720c1452d9f Reviewed-on: https://chromium-review.googlesource.com/c/1329685Reviewed-by:
-
Toon Verwaest authored
Otherwise we may look into the invalid string literal later. Bug: chromium:903527 Change-Id: Ieeb3807bd05e532224e04a59878f5dac24e19579 Reviewed-on: https://chromium-review.googlesource.com/c/1329691 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
Georg Neis authored
A missing negation (typo in previous refactoring) had effectively disabled this optimization. Bug: chromium:904104 Change-Id: I3f8d26c7594fcaa762e0a9c992b4cb0bf1bc53f6 Reviewed-on: https://chromium-review.googlesource.com/c/1329690Reviewed-by:
-
Toon Verwaest authored
Bug: chromium:904275 Change-Id: I82712f70954246c16846f44bb9e8dc6e60e73d83 Reviewed-on: https://chromium-review.googlesource.com/c/1329686Reviewed-by:
-
Toon Verwaest authored
Bug: chromium:903874 Change-Id: If9828ae206b9bc1407e7d3f217d5fb894a4fe747 Reviewed-on: https://chromium-review.googlesource.com/c/1329688Reviewed-by:
-
Georg Neis authored
Split the Install methods into PrepareInstall and Install, such that all heap mutations (besides the actual installation) are done in PrepareInstall and only the actual installation in Install. This ensures that the code object in question doesn't get deoptimized while we're still installing its dependencies. Bug: chromium:903697 Change-Id: I4da97d89d0707fa3c00c97c092af0d0faa7a4946 Reviewed-on: https://chromium-review.googlesource.com/c/1329162Reviewed-by:
-
Jakob Kummerow authored
By matching ZoneHandleSet's internals to Handle's internals, we can avoid a few unnecessary casts, and get rid of a few more occurrences of Object**. Bug: v8:3770 Change-Id: I24d6bad3a4959d977abf1f6b8db9be50bb2bc6d8 Reviewed-on: https://chromium-review.googlesource.com/c/1330907 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
- 11 Nov, 2018 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/5d50916..f2c3502 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/af0ede1..ddbeac1 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ie5eb9348ac4bec24bdd4b7c42cc64199ef55b90d Reviewed-on: https://chromium-review.googlesource.com/c/1330919Reviewed-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@{#57417}
-
- 10 Nov, 2018 3 commits
-
-
Sergiy Byelozyorov authored
This is needed so that cctest is built for the Memory perf benchmark. Marking v8_achive as testonly is necessary to be able to depend on the cctest, which is testonly already. R=machenbach@chromium.org Bug: chromium:903562 Change-Id: If5baf3e75226282110999dfa2bd83d475b63258c Reviewed-on: https://chromium-review.googlesource.com/c/1330912Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#57416}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/3f61809..81ffd00 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/93cd73d..af0ede1 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I4d9b172f6657d33629a021475290869f743c5482 Reviewed-on: https://chromium-review.googlesource.com/c/1330911 Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by:
-
Jakob Kummerow authored
as part of the ongoing quest to get rid of Object**/Object* entirely. Bug: v8:3770 Change-Id: Ibe05801fad78b26ca27b044c8091a26ccab5469a Reviewed-on: https://chromium-review.googlesource.com/c/1330909Reviewed-by:
-
- 09 Nov, 2018 8 commits
-
-
chrome://tracingDeepti Gandluri authored
Currently, the tracing for background tasks is quite cryptic when looking at chrome://tracing. Most tasks that are posted appear as ThreadControllerImpl::RunTask, which when looking at other threads can be deduced as compile tasks. Improve instrumentation to be more indicative of the work being done. BUG:v8:8423 Change-Id: I9b5469154ff7163d743efb1df998ca1df08cd4ce Reviewed-on: https://chromium-review.googlesource.com/c/1330012 Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by:
-
tzik authored
This CL moves RunSingleMicrotask with no logic change as a non-essential part of the following CL, in order to reduce the following CL size. Change-Id: I93e4aa860710c169c0474ee28ada083139d2b607 Reviewed-on: https://chromium-review.googlesource.com/c/1328552 Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Reviewed-by:
-
tzik authored
This CL moves EnqueueMicrotask and RunMicrotasks builtins out of InternalBuiltinAssembler to a separate class with no logic change. This is a trivial part of the following "Implement Faster MicrotaskQueue Step 2" https://crrev.com/c/1290751 in order to clean up the diff for easier review, and also for unblocking other CLs. Change-Id: I34dda8e599ffbf4db4bae07d3fd8ea3d6fadeb6b Reviewed-on: https://chromium-review.googlesource.com/c/1328548Reviewed-by:
-
Frank Tang authored
All intl/regress-8413-* tests are super slow on native arm: So remove them now. NOTRY=true Bug: v8:8435 Change-Id: I2d07ce00332d8323777f0a1aed5235b6f9c7f123 Reviewed-on: https://chromium-review.googlesource.com/c/1328645Reviewed-by:
-
Adam Klein authored
Now that intl.js is gone, there's no particular reason to worry about Intl features accidentally using RegExp objects in a way that would be visible to author code. Bug: v8:5751 Change-Id: I7bb274ed124ac593ab5f4f6995941f11a0ded480 Reviewed-on: https://chromium-review.googlesource.com/c/1325030Reviewed-by:
-
Adam Klein authored
This test was adapted from a repro, and thus it's rather complex. It takes over seven minutes to run on the arm64 sim debug bot, and nearly five minutes on arm. Given that it was originally accompanied by a very targeted fix in Crankshaft, it strikes me that this probably isn't worth our CPU time to continue running. Bug: v8:7783, chromium:85177 Change-Id: Ibe85cc254aa754365404b5fbbf80bcb1f5a09c68 Reviewed-on: https://chromium-review.googlesource.com/c/1327188Reviewed-by:
-
Toon Verwaest authored
No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I287197c8603e9e550d7f4832c1f85009136f4bb0 Reviewed-on: https://chromium-review.googlesource.com/c/1329961 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
The flag is on by default, so we don't need to specify it. More importantly, the tests are expected to work for any value of that flag. So don't force the flag but use whatever the test variant chooses. Note that in streaming-compile.js, the flag was accidentally specified as '-async-compilation'. I also removed that one. R=ahaas@chromium.org Change-Id: Ifad31160d266dda38cdd9dd1d73dad69bd2c2f2c Reviewed-on: https://chromium-review.googlesource.com/c/1325961Reviewed-by:
-
