- 01 Jul, 2019 4 commits
-
-
Yu Yin authored
regress-976627 is pass and should pass on mips64el, see 4c156936 https://crrev.com/c/1674027 Change-Id: I4da905ea129a78988d75e5b19cca3a4e5a17fdcb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679960 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Auto-Submit: Yu Yin <xwafish@gmail.com> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#62459}
-
Leszek Swirski authored
The previous fix for this bug (crrev.com/c/1678365) pessimistically would mark all shadowed variables as maybe_assigned. Unfortunately, this doesn't work across a parse/preparse boundary, where the shadowing variable is found via Scope::AnalyzePartially while the shadowed variable is outside of the preparser entry point. In those cases, the referencing proxy is copied to the outer scope, in which case the dynamicness of the original lookup is lost and the maybe_assigned pessimisation no longer applies. This means that maybe_assigned status of a variable is dependent on which function is being parsed. In particular, it can cause bytecode to change on recompilation, causing issues for lazy source positions. This patch allows SetMaybeAssigned to walk its shadowed variables, and recursively set them to maybe_assigned too. Checking for maybe_assigned changing prevents this recursion from having a quadratic performance failure mode. Bug: v8:8510 Bug: v8:9394 Change-Id: Id19fe1fad5ec8f0f9aa03b00eb24497f88f71216 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1677265 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#62458}
-
Z Nguyen-Huu authored
When applying Object.seal(), Object.freeze() to Smi, Double elements kind, it will transition to Object elements kind first then to new frozen, sealed elements kind accordingly. Also, add more mjsunit. Bug: v8:6831 Change-Id: I454b42d7eb329b03e20245896641eb6c1a87831d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1662657 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#62457}
-
Jaroslav Sevcik authored
This reverts commit 16c1cb83. Reason for revert: ClusterFuzz failure Original change's description: > [turbofan] Serialize source position table > > ... for concurrent graph building. > > Bug: v8:7790 > Change-Id: I55eb419bda843670eff7de31e942dd8406c792f9 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1682027 > Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> > Reviewed-by: Georg Neis <neis@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62455} TBR=jarin@chromium.org,neis@chromium.org,mslekova@chromium.org Change-Id: Ib8ecd9f4e654b34036ad3157910e19d8ef034c52 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7790 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1682571Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#62456}
-
- 30 Jun, 2019 2 commits
-
-
Jaroslav Sevcik authored
... for concurrent graph building. Bug: v8:7790 Change-Id: I55eb419bda843670eff7de31e942dd8406c792f9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1682027 Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
-
Sigurd Schneider authored
Trying to get luci.v8.ci/Linux%20V8%20FYI%20Release%20(NVIDIA) to pass after failure: https://ci.chromium.org/p/v8/builders/luci.v8.ci/Linux%20V8%20FYI%20Release%20(NVIDIA)/5698 Suspicion is that this is failure is not V8 related. This failure is blocking LKGR. TBR=machenbach@chromium.org Change-Id: Idac4c412f8b14a8b08e0cff4aeafec959dd38453 Notry: true Change-Id: Idac4c412f8b14a8b08e0cff4aeafec959dd38453 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1682569 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#62454}
-
- 29 Jun, 2019 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/024e273..666dc4c [js-api] Use IDL conventions around ambient values. (#1037) (Ms2ger) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/666dc4c TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: I49216e2f2f2a36bc6f2d29adaa40f88b9ada1be0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1683108Reviewed-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@{#62453}
-
- 28 Jun, 2019 19 commits
-
-
Francis McCabe authored
This reverts commit 99fd5b9b. Reason for revert: fails presubmit test: https://ci.chromium.org/p/v8/builders/ci/V8%20Presubmit/5238 and a nosnap test https://ci.chromium.org/p/v8/builders/ci/V8%20Win32%20-%20nosnap%20-%20shared/34143 Original change's description: > Let all early errors be SyntaxErrors. > > Implement the spec change from the following TC39 PR: > https://github.com/tc39/ecma262/pull/1527 > > Bug: v8:9326 > Change-Id: I9639903b12e7621e323990e2335f00e0313a59c3 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1643171 > Reviewed-by: Adam Klein <adamk@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Commit-Queue: Adam Klein <adamk@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62451} TBR=adamk@chromium.org,verwaest@chromium.org,rkirsling@gmail.com Change-Id: If63b97725e9737ad5a98800e1194caf8e9c1c43d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9326 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1682393Reviewed-by:
Francis McCabe <fgm@chromium.org> Commit-Queue: Francis McCabe <fgm@chromium.org> Cr-Commit-Position: refs/heads/master@{#62452}
-
Ross Kirsling authored
Implement the spec change from the following TC39 PR: https://github.com/tc39/ecma262/pull/1527 Bug: v8:9326 Change-Id: I9639903b12e7621e323990e2335f00e0313a59c3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1643171Reviewed-by:
Adam Klein <adamk@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#62451}
-
Frank Tang authored
1. Move the reading of Notation before calling SetNumberFormatDigitOptions() ( sync after https://github.com/tc39/proposal-unified-intl-numberformat/pull/37) 2. Sync SetNumberFormatDigitOptions to the spec. 3. Consider the case that while RoundingType is "compact-rounding" do not set the precision. 4. correct the tests accordingly. 5. Fix the rounding of notation: "compact" and put regression cases into test/intl/regress-9408.js Bug: v8:9408 Change-Id: I78d66601fe21b1a74a50047b2abe6a2838a58b8c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681599 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#62450}
-
Frank Tang authored
Measure speed regression of a range of char in complex regexp The measurement is using the code from chromium:977003 To measure python -u tools/run_perf.py --binary-override-path out/x64.release/d8 \ test/js-perf-test/RegExp.json Run on three setting: a. m74 based on tag 7.4.301 b. trunk (m77) c. apply cl 1674851 on trunk ComplexCaseInsensitiveTest-RegExp Score is better if higher Score imp % comp to m74 m74 22910 23430 23360 Trunk (m77) 15190 66.30% 15710 67.05% 15570 66.65% CL 1674851 24590 161.88% 107.33% 24690 157.16% 105.38% 24200 155.43% 103.60% Bug: chromium:977003 Change-Id: I7756f4739c44a07949103650565d1ca902e1b7ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679651Reviewed-by:
-
Ross McIlroy authored
This allows us to use this flag to specify the local location of a shared library when processing a trace run on Android. Change-Id: I3aa44beaed700b8c5354af12a4df176aa1cbfd0c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681137 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Auto-Submit: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#62448}
-
Sigurd Schneider authored
for in the register allocation. NOTE: This is expected to cause performance regressions, but we enable it so that we can land small tweaks on top of it and get immediate performance feedback. Change-Id: I062f98a3ee6702509e870cc110096a3bdf53a6fd Bug: v8:9088 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681133 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Auto-Submit: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Raphael Kubo da Costa authored
IWYU. This also fixes the libstdc++ build after commit 6056c0dc ("Make adding crash keys thread safe"): ../../v8/src/diagnostics/crash-key.cc:36:15: error: no template named 'atomic' in namespace 'std' static std::atomic<int> last{-1}; ~~~~~^ Bug: chromium:957519 Change-Id: Ib1f465dc5e4f0b4a212486a9a3bebe54bb6654b3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681129 Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Maciej Goszczycki authored
This is a reland of 24ac9a9a Fixed an msvc warning. Original change's description: > [roheap] Enable shared ro-heap by default if ptr compression is disabled > > Shared read-only heap is currently incompatible with pointer compression. > Enable sharing only if pointer compression is disabled. > > Bug: v8:7464 > Change-Id: I0866ac288a34eb92fc227e8beba57f4d72a69ef0 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1635509 > Reviewed-by: Dan Elphick <delphick@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Commit-Queue: Maciej Goszczycki <goszczycki@google.com> > Cr-Commit-Position: refs/heads/master@{#61963} Bug: v8:7464 Change-Id: Ieb5fefe8be1f94e0ac8e769d73de21427559ccab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681128Reviewed-by:
Dan Elphick <delphick@chromium.org> Commit-Queue: Maciej Goszczycki <goszczycki@google.com> Cr-Commit-Position: refs/heads/master@{#62445}
-
Igor Sheludko authored
The latter is better because it takes field type into account when decompressing field value. Drive-by: use [DECL_]ACCESSOR macros for some fields. Bug: v8:9353 Change-Id: I3d7f07d11b1e379e3e6cf0310d836af6b48c1338 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680539 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#62444}
-
Darius Mercadier authored
To choose the evacuation candidates, all the pages were put in a vector, then sorted, and then only select if, among other thing, they had enough free bytes in them. It meant sorting a lot of pages that couldn't be selected. With this CL, only the pages with enough free bytes are put in the vector, which should (slightly) improve the time needing to select the evacuation candidates. Bug: v8:9329 Change-Id: I0261fe3554c0bf75136a84a35d5c6a231762afe8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680554Reviewed-by:
-
Johannes Henkel authored
New Revision: 8b7ea912e516a6daa61487c700687a9426e3a396 Update v8 files / build config accordingly. - There's now a new library in third_party/inspector_protocol, bindings/bindings.h, which is configured much like encoding/encoding.h. It doesn't have much stuff in it yet, but will soon get more code that would otherwise need to go into jinja templates. It also comes with a new test, only a smoke test thus far. Change-Id: I9c00a54a840c214b4bb744a3b272e5ce221954fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1678273Reviewed-by:
Alexei Filippov <alph@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#62442}
-
Yang Guo authored
TBR=jgruber@chromium.org Bug: v8:9247 Change-Id: I8024f701eae2a8b0d60fe859503089dd76b4d5bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681123Reviewed-by:
-
Ulan Degenbaev authored
The flag configures both the young and old generation limits. Bug: v8:9306 Change-Id: Ib94dcb6dc014864248a5926f585b54a83db28063 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679500Reviewed-by:
Hannes Payer <hpayer@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#62440}
-
Mathias Bynens authored
Instead of conditionally normalizing file paths, go back to using the basename in the dynamically-generated regular expression pattern. Bug: v8:7950, v8:9395, v8:9406 Change-Id: I57d2449a8229a67b038c7fcffe36218848d9a575 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681122Reviewed-by:
Tamer Tas <tmrts@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#62439}
-
Yu Yin authored
port e304d80e https://crrev.com/c/1660618 Original Commit Message: powered by a new function Execution::CallWasm and a corresponding, Turbofan-generated CWasmEntry stub. This entirely sidesteps the traditional Execution::Invoke -> JSEntryStub path. Change-Id: I4d3a284779ecff27e39fffb658c608b16c43d828 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679962 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
Yang Guo authored
TBR=luoe@chromium.org Bug: chromium:976713 Change-Id: Ib92c6054a017a94ad23721de240b8a20d87c9f85 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680544Reviewed-by:
-
Sigurd Schneider authored
..until issue is resolved. TBR=jarin@chromium.org Change-Id: I304ab6bf2c4dcb28af022e07c7fc4719c5239d82 Bug: v8:9404 Notry: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681121 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/b568df7..024e273 [js-api] Remove incorrect note about object caching. (#1036) (Ms2ger) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/024e273 TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: I167825682594ae758aa62098d18119cdbc4fee96 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681320Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/deba8b5..f9c4d9d Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/d16c410..ac493ee TBR=machenbach@chromium.org,sergiyb@chromium.org,tmrts@chromium.org Change-Id: Ic3b556f79d3a7b9c5fe332ac418dc4fce0e995e2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1681319Reviewed-by:
-
- 27 Jun, 2019 14 commits
-
-
Daniel Clark authored
This change is a partial implementation of Synthetic Module Record as specified here: https://heycam.github.io/webidl/#synthetic-module-records This includes: - Introduce SyntheticModule class inheriting from Module. - Extend v8::Module interface in v8.h to include Synthetic Module APIs, with corresponding implementations in api.cc. - Provide SyntheticModule implementations of PrepareInstantiate, FinishInstantiate, and SetExport. - Provide cctest unit tests for the implementations in the preceding item. We will follow up with further submissions to implement the remaining members of SyntheticModule (ResolveExport and Evaluate). Bug: v8:9292 Change-Id: I25b1b695b5d1c3004677cd685f0dfd95283438fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1626829 Commit-Queue: Dan Clark <daniec@microsoft.com> Reviewed-by:
-
Adam Klein authored
Add gdeepti and bbudge, remove aseemgarg. Change-Id: I87a9e0b36b1233aae5fb72d019e9b8b413d10f9e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680799Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#62432}
-
Z Nguyen-Huu authored
GetPropertyWithReceiver is similar to GetProperty, except that additional receiver parameter is used in TryPrototypeChainLookup to support GetPropertyWithReceiver stub. We only use this stub in ProxyGetProperty builtin for now. Bug: v8:8958 Change-Id: Ied60e4f6ee6e09bca2f161048b481a0bf37a78a7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1676879 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#62431}
-
Ng Zhi An authored
Bug: None Change-Id: Idc7857342e9249d66473ab4af1044e1cd2cab5a6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680788Reviewed-by:
-
Milad Farazmand authored
Port e304d80e Original Commit Message: powered by a new function Execution::CallWasm and a corresponding, Turbofan-generated CWasmEntry stub. This entirely sidesteps the traditional Execution::Invoke -> JSEntryStub path. R=jkummerow@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I87c85f3506c4e4dae12e462dd3c7790bc9ab25d1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680798Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#62429}
-
Georg Neis authored
This reverts commit a05bcc3a. Reason for revert: Still issues with maybe_assigned, blocking roll. Original change's description: > Reland "Enable lazy source positions by default" > > Second attempt to reland 69fafb5f > now that the maybe_assigned bug is fixed. > > > Original change's description: > > Enable lazy source positions by default > > > > Also adds a compile time flag which allows the default to be configured > > so node can disable it since it hangs the node cpu profiler tests. > > > > Bug: v8:8510 > > Change-Id: Idf4785036dc6242769410091518a67ac9179b718 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1491491 > > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > > Commit-Queue: Dan Elphick <delphick@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#62089} > > Bug: v8:8510 > Change-Id: Ia6d5d1d3a3c2b6a14c70ee67b02bec62a6a1a1d4 > Cq-Include-Trybots: luci.v8.try:v8_linux_gc_stress_dbg, v8_linux64_gc_stress_custom_snapshot_dbg_ng > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1679498 > Commit-Queue: Dan Elphick <delphick@chromium.org> > Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#62411} TBR=rmcilroy@chromium.org,delphick@chromium.org Change-Id: I52b2924e05ff87f6469be4723e5e13979d1aeffa No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8510 Cq-Include-Trybots: luci.v8.try:v8_linux_gc_stress_dbg, v8_linux64_gc_stress_custom_snapshot_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680553Reviewed-by:
-
Maciej Goszczycki authored
Bug: v8:7464 Change-Id: Ieab0007b477894fb8e4c662e584b54cb1e288041 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680549 Commit-Queue: Maciej Goszczycki <goszczycki@google.com> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#62427}
-
Francis McCabe authored
This reverts commit 24ac9a9a. Reason for revert: compilation failures on windows. See https://ci.chromium.org/p/v8/builders/ci/V8%20Win32%20-%20builder/29313 Original change's description: > Reland "[roheap] Enable shared ro-heap by default if ptr compression is disabled" > > This is a reland of fb4d5480 > > Few test-serialize tests were not clearing the shared heap before using a > new snapshot, breaking the noembed build. This is fixed now and a check > has been added > (https://chromium-review.googlesource.com/c/v8/v8/+/1667415) to make > sure it doesn't happen again. > > Original change's description: > > [roheap] Enable shared ro-heap by default if ptr compression is disabled > > > > Shared read-only heap is currently incompatible with pointer compression. > > Enable sharing only if pointer compression is disabled. > > > > Bug: v8:7464 > > Change-Id: I0866ac288a34eb92fc227e8beba57f4d72a69ef0 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1635509 > > Reviewed-by: Dan Elphick <delphick@chromium.org> > > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > > Commit-Queue: Maciej Goszczycki <goszczycki@google.com> > > Cr-Commit-Position: refs/heads/master@{#61963} > > Bug: v8:7464 > Change-Id: Ie7d09cebf897a3f0e4a6c103ad0c132c4faf6c6e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1667418 > Reviewed-by: Dan Elphick <delphick@chromium.org> > Commit-Queue: Maciej Goszczycki <goszczycki@google.com> > Cr-Commit-Position: refs/heads/master@{#62425} TBR=delphick@chromium.org,goszczycki@google.com Change-Id: Ia96e2f13b502f96315ac2ed3447373c7b5774c6a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7464 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680659Reviewed-by:
-
Maciej Goszczycki authored
This is a reland of fb4d5480 Few test-serialize tests were not clearing the shared heap before using a new snapshot, breaking the noembed build. This is fixed now and a check has been added (https://chromium-review.googlesource.com/c/v8/v8/+/1667415) to make sure it doesn't happen again. Original change's description: > [roheap] Enable shared ro-heap by default if ptr compression is disabled > > Shared read-only heap is currently incompatible with pointer compression. > Enable sharing only if pointer compression is disabled. > > Bug: v8:7464 > Change-Id: I0866ac288a34eb92fc227e8beba57f4d72a69ef0 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1635509 > Reviewed-by: Dan Elphick <delphick@chromium.org> > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> > Commit-Queue: Maciej Goszczycki <goszczycki@google.com> > Cr-Commit-Position: refs/heads/master@{#61963} Bug: v8:7464 Change-Id: Ie7d09cebf897a3f0e4a6c103ad0c132c4faf6c6e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1667418Reviewed-by:
-
Jakob Kummerow authored
powered by a new function Execution::CallWasm and a corresponding, Turbofan-generated CWasmEntry stub. This entirely sidesteps the traditional Execution::Invoke -> JSEntryStub path. Change-Id: If2b97825cca4ce927eecbddc248c64782d903287 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1660618 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#62424}
-
Hannes Payer authored
Bug: v8:9093 Change-Id: I7c415fd0ea9e48f7ee189115f164825cb120695b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1624213 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
-
Sigurd Schneider authored
The macro pn ensures that TurboFan nodes can be easily printed in gdb, even in release builds where Node::Print is sometimes not available (because all uses have been inlined). This CL also modifies the print function to deal gracefully with nullptr input nodes, which is helpful for debugging. Change-Id: Ib5f58aa13b719c8390826bc89dfe21cf58586de5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1672941Reviewed-by:
-
Mathias Bynens authored
d8 treats files with the .mjs extension as modules instead of classic scripts. Thus, the `// MODULE` pragma and its corresponding logic in test runners can be removed in favor of explicitly adding the extension. Bug: v8:7950, v8:9395, v8:9406 Also-By: tmrts@chromium.org Change-Id: Ic74328dc5c5f176bb4bdf6d74bdd4d3966279ba5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1675958 Commit-Queue: Mathias Bynens <mathias@chromium.org> Reviewed-by:
-
Michael Lippautz authored
Previously, the early bailout for incremental marking only considered V8's memory which does not work when a big porition of memory is actually allocated globally. Bug: chromium:948807 Change-Id: Ie85c3c68f2b677ef87aba9e70ae74e65783a1fac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1680542Reviewed-by:
-
