- 13 Aug, 2018 26 commits
-
-
Camillo Bruni authored
Bug: v8:6922 Change-Id: I641f654f0548c2da24cdea3ffd275461ae8ce9b0 Reviewed-on: https://chromium-review.googlesource.com/1172776Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#55098}
-
Benedikt Meurer authored
The DataView access methods can use the neutering protector to avoid introducing an explicit check into the optimized code to see if the backing store was neutered. Instead the optimized code has an implicit dependency on the global neutering protector which gets invalidated when the first array buffer is neutered (globally). We use the same trick for typed arrays already. Bug: chromium:225811 Change-Id: I9b3c95b3113b8fa00dcbba216ef29c84c0056951 Reviewed-on: https://chromium-review.googlesource.com/1172779 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#55097}
-
Toon Verwaest authored
[scanner] Explicitly add one-byte characters to a one-byte literal buffer when scanning ascii identifiers Change-Id: Ia8337506d9f442d6887b6fa3c2ed17210ffd3c28 Reviewed-on: https://chromium-review.googlesource.com/1172789Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#55096}
-
Toon Verwaest authored
Change-Id: I0d23484d9a48a73575ca158b07b7ed1b83d4029e Reviewed-on: https://chromium-review.googlesource.com/1172774Reviewed-by:
-
Bogdan Lazarescu authored
Change-Id: I4a6d57903016323eba439cd7f959f263d6605c84 Reviewed-on: https://chromium-review.googlesource.com/1169165Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Bogdan Lazarescu <bogdan.lazarescu@arm.com> Cr-Commit-Position: refs/heads/master@{#55094}
-
Tobias Tebbi authored
drive-by change: fix wrong typing in CSA. Change-Id: I9234306e8568a64157b44a86a58f09e65116b298 Reviewed-on: https://chromium-review.googlesource.com/1172583 Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#55093}
-
Clemens Hammacher authored
After https://crrev.com/c/1172285, abortion and deletion of an {AsyncCompileJob} is the same. Hence, remove the {AbortCompileJobsOnIsolate} method and replace all uses by {DeleteCompileJobsOnIsolate}. R=ahaas@chromium.org CC=mstarzinger@chromium.org Bug: chromium:869420 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: I053dc47395a257066bbca55069d53445dc28eeb9 Reviewed-on: https://chromium-review.googlesource.com/1172288Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#55092}
-
Camillo Bruni authored
This should make the uses of binary vs. bitwise not very clear: - Word32BinaryNot for logical negation - Word32BitwiseNot for bitwise negation Change-Id: I3345913111da0dbdae6fdf285f090b67eb3f3afc Reviewed-on: https://chromium-review.googlesource.com/1169205 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#55091}
-
Toon Verwaest authored
Change-Id: If008d618d3cb27c38cf814b1858244578d0c4e84 Reviewed-on: https://chromium-review.googlesource.com/1169213Reviewed-by:
-
Bret Sepulveda authored
This patch also includes some CSS tweaks and other minor cleanup. Bug: v8:6240 Change-Id: I86e26fe53465dff6f9a706f58e565b1f1ee559da Reviewed-on: https://chromium-review.googlesource.com/1172360 Commit-Queue: Bret Sepulveda <bsep@chromium.org> Reviewed-by:
-
Camillo Bruni authored
Bug: chromium:840785 Change-Id: I043df7aa5203dec27b84636c64286d68a56fba31 Reviewed-on: https://chromium-review.googlesource.com/1172428Reviewed-by:
Dan Elphick <delphick@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#55088}
-
jgruber authored
Bug: v8:8015 Change-Id: Ie8265458ace8c0d12ca9d3f58afd981f1f30cd1e Reviewed-on: https://chromium-review.googlesource.com/1170826 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Andreas Haas authored
{AsyncCompileJob::FinishCompile} assumes that it is called within a {HandleScope}. This was not the case when it was called at the end of streaming compilation. R=clemensh@chromium.org Bug: chromium:860637 Change-Id: I74508e6cdfc145efb9adc76176abce1ca5713515 Reviewed-on: https://chromium-review.googlesource.com/1172357Reviewed-by:Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#55086}
-
Predrag Rudic authored
By using NAL for reading PC instead of BAL, we are acctualy not taking branch. Thus optimizing code for instruction pipeline and address predictor. Change-Id: I574dc98390dc850443de06c928022292e2b50747 Reviewed-on: https://chromium-review.googlesource.com/1170777Reviewed-by:
Ivica Bogosavljevic <ibogosavljevic@wavecomp.com> Commit-Queue: Ivica Bogosavljevic <ibogosavljevic@wavecomp.com> Cr-Commit-Position: refs/heads/master@{#55085}
-
Yang Guo authored
This simplifies a bit. R=jgruber@chromium.org Change-Id: If7a433c9d2b13edf4fe4485816ac5ab06435773e Reviewed-on: https://chromium-review.googlesource.com/1172299Reviewed-by:
-
Clemens Hammacher authored
In {WasmEngine::DeleteCompileJobsOnIsolate} (triggered on isolate teardown), we are deleting the {AsyncCompileJob} with the expectation that this cancels all background compilation. Since the introduction of the CompilationState, this is not true any more. The call to {CompilationState::Abort} is missing. This CL fixes this by moving the logic from {AsyncCompileJob::Abort} to {~AsyncCompileJob}, since the former calls the latter anyway. R=ahaas@chromium.org Bug: chromium:869420 Change-Id: I4644d161270def0fe3a94d09cde0135ee420a383 Reviewed-on: https://chromium-review.googlesource.com/1172285Reviewed-by: -
Camillo Bruni authored
Bug: chromium:840785 Change-Id: I93f417084cc3ad3d1b906bdbef5dda14ead208c6 Reviewed-on: https://chromium-review.googlesource.com/1169044Reviewed-by:
-
Jaroslav Sevcik authored
Bug: v8:7790 Change-Id: I7c55b81a21ef4bafd9ed9b1e6c68bd9110850b11 Reviewed-on: https://chromium-review.googlesource.com/1172135Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#55081}
-
Ross McIlroy authored
Decodes SFI::Flags on construction and sets properties in ParseInfo::flags_ directly, as well as adding a FunctionKind field, instead of keeping the encoded SFI flags in the ParseInfo. BUG=v8:8041 Change-Id: I9bd9345b29a8b0e9ffb3e2e73aac11ae6ef69322 Reviewed-on: https://chromium-review.googlesource.com/1169181Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#55080}
-
Clemens Hammacher authored
All these methods did was executing DCHECKs. This CL just writes out the DCHECKs directly. R=mstarzinger@chromium.org Bug: v8:8015 Change-Id: I01d4c536ea354d158da5f628aeab35fb13b80a58 Reviewed-on: https://chromium-review.googlesource.com/1170822 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#55079}
-
Bret Sepulveda authored
This patch reshuffles the colors used for the various tick categories in the visualization. Category rows are now light gray. The new colors are taken from the Material palette. See screenshots on the associated bug. This patch also labels the GC bucket as such, instead of having the same label as uncategorized C++. Bug: v8:6240 Change-Id: I3909a177148b98e99d63f5ec9ae02e3c6f63eb24 Reviewed-on: https://chromium-review.googlesource.com/1172139 Commit-Queue: Bret Sepulveda <bsep@chromium.org> Reviewed-by:
-
Simon Zünd authored
R=jgruber@chromium.org Bug: chromium:873555 Change-Id: I6268bedf47a89194875d1179e603bcfe972c9d68 Reviewed-on: https://chromium-review.googlesource.com/1172282Reviewed-by:
-
Andreas Haas authored
With the origin trial for WebAssembly threads, threads can be turned on and off by the embedder depending on the context we are currently in. With this CL we call the embedder callback stored on the isolate to determine whether threads are enabled in the current context or not. Design decision: I decided to extend the {WasmFeaturesFromIsolate} function to ask the embedder if WebAssembly threads are enabled. This is the function which defines dynamically which features are turned on. It would be awkward to have two such functions, one which calls the embedder and one which does not. A downside is that in WasmJs::Install the embedder does not seem to be ready to be called. That's why I changed the code there to call {WasmFeaturesFromFlags} instead. R=titzer@chromium.org, mstarzinger@chromium.org Bug: chromium:868844 Change-Id: I6bfa89960a54cec71992756e3717bbb3a9fe195e Reviewed-on: https://chromium-review.googlesource.com/1169180 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#55076}
-
Ivica Bogosavljevic authored
This CL implements several things needed for full SIMD BE support in WASM: * Global variables are now kept in little-endian order as per specification * Added support for SIMD on BE in wasm interpreter * Fixed several tests that didn't work on BE because input or output data were not using LE in-memory layout Change-Id: I4542d13d09fd276e15b0fc39f02e4a58831f65e4 Reviewed-on: https://chromium-review.googlesource.com/1160484 Commit-Queue: Ivica Bogosavljevic <ibogosavljevic@wavecomp.com> Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
Aseem Garg <aseemgarg@chromium.org> Cr-Commit-Position: refs/heads/master@{#55075}
-
Yang Guo authored
The break id is no longer used. Bug: v8:5530 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: Ib07046d66497cbd5e01a8a1248afd890180200bf Reviewed-on: https://chromium-review.googlesource.com/1172136Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/68bf4b8..6705895 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Id30b10fbbbe7d29edb71f08d02e9641ae777f52a Reviewed-on: https://chromium-review.googlesource.com/1172151 Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by:
V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#55073}
-
- 12 Aug, 2018 1 commit
-
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/5c13474..68bf4b8 Rolling v8/third_party/fuchsia-sdk: https://chromium.googlesource.com/chromium/src/third_party/fuchsia-sdk/+log/1da4e38..74c827a TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ia676fa56d262206c40bcabfe479a3f74159a1eec Reviewed-on: https://chromium-review.googlesource.com/1172077 Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by:
-
- 11 Aug, 2018 7 commits
-
-
Sergiy Byelozyorov authored
TBR=sergiyb@chromium.org No-Try: true Bug: chromium:826280 Change-Id: I8225cd481835470235496d38023794068980dc3d Reviewed-on: https://chromium-review.googlesource.com/1171240Reviewed-by:
Sergiy Byelozyorov <sergiyb@chromium.org> Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#55071}
-
Sergiy Byelozyorov authored
TBR=sergiyb@chromium.org No-Try: true Bug: chromium:826280 Change-Id: Ica0061605b76c699516a0bc83e14cb7ed744346e Reviewed-on: https://chromium-review.googlesource.com/1171236Reviewed-by:
-
Sergiy Byelozyorov authored
TBR=sergiyb@chromium.org No-Try: true Bug: chromium:826280 Change-Id: Ia68c012ee80ce99982c9561dedcab3c4a6bb14e0 Reviewed-on: https://chromium-review.googlesource.com/1171235 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
-
Sergiy Byelozyorov authored
TBR=sergiyb@chromium.org No-Try: true Bug: chromium:775123 Change-Id: Ie1e1f150aa2f7255bd2fc3c3b778620c77c56425 Reviewed-on: https://chromium-review.googlesource.com/1168489 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
-
Sergiy Byelozyorov authored
R=machenbach@chromium.org No-Try: true Bug: chromium:872257 Change-Id: I4de1a9dfccbb0d123c1c42c31a1f697e628623fa Reviewed-on: https://chromium-review.googlesource.com/1171224 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#55067}
-
Ulan Degenbaev authored
This reverts commit 5b434929. Changes after the original CL: - Right-trimming registers the array as an object with invalidated slots. - Left-trimming moves the array start in the invalidated slots map. Original change's description: > Fix invalidation of old-to-old slots after object trimming. > > A recorded old-to-old slot may be overwritten with a pointer to a new > space object. If the object containing the slot is trimmed later on, > then the mark-compactor may crash on a stale pointer to new space. > > This patch ensures that: > 1) On trimming of an object we add it to the invalidated_slots sets. > 2) The InvalidatedSlotsFilter::IsValid returns false for slots outside > the invalidated object unless the page was already swept. > > Array left-trimming is handled as a special case because object start > moves and cannot be added to the invalidated set. Instead, we clear > the freed memory so that the recorded slots contain Smi values. > > Bug: chromium:870226,chromium:816426 > Change-Id: Iffc05a58fcf52ece45fdb085b5d1fd4b3acb5d53 > Reviewed-on: https://chromium-review.googlesource.com/1163784 > Commit-Queue: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Hannes Payer <hpayer@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#54953} Change-Id: I1f1080f680196c581f62aef8d3a00a595f9bb9b0 Reviewed-on: https://chromium-review.googlesource.com/1165555 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#55066}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/f5a5b7b..5c13474 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/bca7d20..21cd5a3 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/15a5a77..6a4e31b TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I05740cbd9d85888d3b6568bb96eac9598cb7d8cc Reviewed-on: https://chromium-review.googlesource.com/1171953 Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Reviewed-by:
-
- 10 Aug, 2018 6 commits
-
-
Michael Achenbach authored
This is a reland of 18c90f48 Original change's description: > [test] Pass suite environment to Android test runner > > TBR=sergiyb@chromium.org > > Bug: v8:8046 > Change-Id: I201f7a7ee119628e14c864602a2d3cbadfc4052b > Reviewed-on: https://chromium-review.googlesource.com/1170779 > Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#55051} NOTRY=true Bug: v8:8046 Change-Id: I73923a2ae532bb7d773c87fd77844b4e655b568c Reviewed-on: https://chromium-review.googlesource.com/1171382 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
Michael Achenbach authored
This is a reland of a4355b77 Original change's description: > [test] Add files not pushed for test on Android > > TBR=neis@chromium.org > NOTRY=true > > Bug: v8:8047 > Change-Id: I6d59cd9137f56a5061d836afb02b33f7b25d4aa0 > Reviewed-on: https://chromium-review.googlesource.com/1170772 > Reviewed-by: Georg Neis <neis@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#55047} TBR=neis@chromium.org NOTRY=true Bug: v8:8047 Change-Id: If273d9407ed17f4de827b08039efe4d5cd34632e Reviewed-on: https://chromium-review.googlesource.com/1171282Reviewed-by:
-
Sathya Gunasekaran authored
Previously, we created a JSObject with a non null prototype for an internal object which isn't what we want as it casues side effects. Bug: chromium:872514 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: I3318044a03318f3d7099f3ba889450c651cea9e1 Reviewed-on: https://chromium-review.googlesource.com/1171186Reviewed-by:
-
Vasili Skurydzin authored
https://bugs.chromium.org/p/v8/issues/detail?id=8043 Bug: v8:8043 Change-Id: Ia671e6ebf9dad7379f57bf55ce47cc6cd12809b6 Reviewed-on: https://chromium-review.googlesource.com/1168085 Commit-Queue: John Barboza <jbarboza@ca.ibm.com> Reviewed-by:
John Barboza <jbarboza@ca.ibm.com> Reviewed-by:
-
Ben Smith authored
|Shell::externalized_contents_| is guarded by |Shell::workers_mutex_|, but wasn't being acquired when the serialize WriteValue call failed. Bug: v8:8034 Change-Id: Idd0448e9f44d6b26c17987405d5d7394449e8bb3 Reviewed-on: https://chromium-review.googlesource.com/1170316Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/heads/master@{#55060}
-
Michael Achenbach authored
This is a reland of 4c094342 Original change's description: > [test] Add logic to run tests on Android > > This adds a new command abstraction for running commands on Android > using dockered devices on swarming. > > The new abstraction handles pushing all required files to the device. > The logic used for pushing and running is reused from the perf runner. > > This adds only the mjsunit test suite. Others will be handled in > follow up CLs. The suite logic is enhanced with auto-detection of files > to be pushed to devices, for e.g. load or import statements. > > Some test cases need an extra resource section for specifying required > files. > > Remaining failing tests are marked in the status files for later > triage. > > Bug: chromium:866862 > Change-Id: I2b957559f07fdcd8c1bd2f7034f5ba7754a31fb7 > Reviewed-on: https://chromium-review.googlesource.com/1150153 > Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org> > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#55041} Bug: chromium:866862 Change-Id: Icf7e04c75d4abeab7254d10ba21240e46b0022ae Reviewed-on: https://chromium-review.googlesource.com/1170643Reviewed-by:
-
