- 30 Nov, 2018 31 commits
-
-
Ross McIlroy authored
This is a reland of 10ea3f8a Original change's description: > [Compiler] Introduce IsCompiledScope which prevents flushing of compiled code > > Introduces a IsCompiledScope object which can be used to check whether a > function is compiled, and ensure it remains compiled for the lifetime > of the scope without being uncompiled by bytecode flushing. The Compile > functions are modified to take a scope so that calling code can ensure > the function remains compiled for the lifetime they require. > > Also, don't allocate a feedback vector for asm-wasm code as this > is never used, and will be reallocated if the asm-wasm code fails to > instantiate the module and we fallback to regular JavaScript. > > Also restructure Compiler::PostInstantiation() to allocate the feedback > vector once, and do the optimized code check before optimizing for > always opt. > > BUG=v8:8395 > > Change-Id: I3f1a71143fcae3d1a0c01eefe91ebb4b8594221a > Reviewed-on: https://chromium-review.googlesource.com/c/1352295 > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57971} TBR=jgruber@chromium.org,mstarzinger@chromium.org Bug: v8:8395 Change-Id: I8dc00798a5680997990c879c3380fe4febd47297 Reviewed-on: https://chromium-review.googlesource.com/c/1357045 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#57982}
-
Jakob Kummerow authored
to the new design. Bug: v8:3770 Change-Id: I63291cc8eccfa1da20e84c6d3e9f48f253409396 Reviewed-on: https://chromium-review.googlesource.com/c/1355627 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#57981}
-
Ujjwal Sharma authored
Cleanup runtime/runtime-intl.cc by removing dead code, namely Runtime_CanonicalizeLanguageTag and Runtime_GetDefaultICULocale. Bug: v8:8439,v8:5751 Change-Id: Id8712b2f3b2ddffc0e289b904f17ae3b09faffae Reviewed-on: https://chromium-review.googlesource.com/c/1329705 Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#57980}
-
Jakob Kummerow authored
Bug: v8:3770 Change-Id: I0ffdd0d9da8629977a0b82fbfdac2b4f903e39ad Reviewed-on: https://chromium-review.googlesource.com/c/1355626Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#57979}
-
Ross McIlroy authored
The optimized code for TestSetWithCustomIterator holds a weak reference to the map for the entries object. If this is collected by the GC then the optimized code deopts which causes the test to fail. To prevent this, hold onto an entires object to keep it's map alive. Change-Id: I5796e74fc1d7c5061bf8c98f7a82fe582d6be76a Reviewed-on: https://chromium-review.googlesource.com/c/1357043Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#57978}
-
Toon Verwaest authored
- Rely more heavily on Token::IsValidIdentifier. - Deal with IsLet() when it's possibly a lexical declaration. - Remove ENUM from the default IsAnyIdentifier range. - Always pre-check whether IsAnyIdentifier before classifying identifiers. Change-Id: I55eae6ff65dc306b466fa29d233c715e85bc3854 Reviewed-on: https://chromium-review.googlesource.com/c/1356514Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#57977}
-
George Wort authored
Add the arm architecture to the list of archs that support Liftoff in mjsunit and so run the Liftoff tests for it. Bug: v8:6600 Change-Id: I4896f0727f6ccc3343f5d517e100840f76dd901d Reviewed-on: https://chromium-review.googlesource.com/c/1357040Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57976}
-
Hannes Payer authored
Bug: chromium:852420 Change-Id: I47ea0994b7f1933095995c051fce76c288a25d6a Reviewed-on: https://chromium-review.googlesource.com/c/1356515 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
-
Ross McIlroy authored
This reverts commit 10ea3f8a. Reason for revert: Causing failure on gc_stress bot: https://logs.chromium.org/logs/v8/buildbucket/cr-buildbucket.appspot.com/8928421099411850688/+/steps/Bisect_10ea3f8a/0/steps/Retry/0/logs/collections-construct../0 Original change's description: > [Compiler] Introduce IsCompiledScope which prevents flushing of compiled code > > Introduces a IsCompiledScope object which can be used to check whether a > function is compiled, and ensure it remains compiled for the lifetime > of the scope without being uncompiled by bytecode flushing. The Compile > functions are modified to take a scope so that calling code can ensure > the function remains compiled for the lifetime they require. > > Also, don't allocate a feedback vector for asm-wasm code as this > is never used, and will be reallocated if the asm-wasm code fails to > instantiate the module and we fallback to regular JavaScript. > > Also restructure Compiler::PostInstantiation() to allocate the feedback > vector once, and do the optimized code check before optimizing for > always opt. > > BUG=v8:8395 > > Change-Id: I3f1a71143fcae3d1a0c01eefe91ebb4b8594221a > Reviewed-on: https://chromium-review.googlesource.com/c/1352295 > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57971} TBR=rmcilroy@chromium.org,mstarzinger@chromium.org,jgruber@chromium.org Change-Id: I1449a02a0aceb9757440757628e586df33972a40 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8395 Reviewed-on: https://chromium-review.googlesource.com/c/1357042Reviewed-by:
-
Clemens Hammacher authored
This has significant impact on validation time (11% regression, see linked bug). These annotations bring us back to the old performance (according to local measurements it even makes us better than before). R=mstarzinger@chromium.org Bug: chromium:910432 Change-Id: I8e701f9577d53115b3db22be2a09487414c965df Reviewed-on: https://chromium-review.googlesource.com/c/1356511Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57973}
-
Hannes Payer authored
Bug: chromium:852420 Change-Id: Ie1f656cafe78c517ff53676d8cb7200d0bf1d7cc Reviewed-on: https://chromium-review.googlesource.com/c/1356518Reviewed-by:
-
Ross McIlroy authored
Introduces a IsCompiledScope object which can be used to check whether a function is compiled, and ensure it remains compiled for the lifetime of the scope without being uncompiled by bytecode flushing. The Compile functions are modified to take a scope so that calling code can ensure the function remains compiled for the lifetime they require. Also, don't allocate a feedback vector for asm-wasm code as this is never used, and will be reallocated if the asm-wasm code fails to instantiate the module and we fallback to regular JavaScript. Also restructure Compiler::PostInstantiation() to allocate the feedback vector once, and do the optimized code check before optimizing for always opt. BUG=v8:8395 Change-Id: I3f1a71143fcae3d1a0c01eefe91ebb4b8594221a Reviewed-on: https://chromium-review.googlesource.com/c/1352295Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Camillo Bruni authored
- Message listener callbacks - Bootstrapper and deserialization - ObjectVerify - Invoke and InvokeApiFunction Drive-by-fix: sort RCS counters list. Change-Id: I9acec3a3b94cb126c23575aae749c60b5257549d Reviewed-on: https://chromium-review.googlesource.com/c/1356509Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#57970}
-
Jakob Gruber authored
Bug: v8:8503, v8:7777 Change-Id: Iadf515cf4735d1046c7c14f44c02d5d5f95df87a Reviewed-on: https://chromium-review.googlesource.com/c/1356512Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#57969}
-
Clemens Hammacher authored
Do not implement one-armed ifs by emulating an empty else branch. In Liftoff, we can generate better code and save compile time by handling this specially. If the merge point at the end of the if is not reached by the if-branch, we do not need to generate any merge code. R=titzer@chromium.org Bug: v8:6600, v8:8423 Change-Id: Ie8ea69dd7491f225605a8e1b986d275d869aa90b Reviewed-on: https://chromium-review.googlesource.com/c/1356508 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#57968}
-
Tobias Tebbi authored
Change-Id: I9c927567e43e269a9b8ed81edfc8786a879e9573 Reviewed-on: https://chromium-review.googlesource.com/c/1350120Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#57967}
-
Sigurd Schneider authored
Change-Id: Id73e9e4862d3b7751b6867183a43cfa7a0cdef52 Bug: v8:8344 Reviewed-on: https://chromium-review.googlesource.com/c/1355145 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Peter Marshall authored
Bug: chromium:906043 Change-Id: I3a397447be186eff7e6b2ab25341718b6c0d205d Reviewed-on: https://chromium-review.googlesource.com/c/1356507 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
-
Maya Lekova authored
Remove the test-api/InitializeDefaultIsolateOnSecondaryThread_ResourceConstraints test which was setting max-old-space-size limit without acutally using it. This caused repetitive failures, resulting in the test being effectively disabled. Bug: v8:8521 R=ulan@chromium.org, yangguo@chromium.org Change-Id: Iad39cc95df86963d256816bf56d0bc5f62f7d5c9 Reviewed-on: https://chromium-review.googlesource.com/c/1356506Reviewed-by:
-
Yang Guo authored
Termination exceptions tear down V8 to the bottom-most V8 call. If there is a v8::TryCatch scope around that call, it returns true for HasTerminated() and HasCaught(). However, Isolate::IsExecutionTerminating() returns false and we can call into V8 from still inside the v8::TryCatch scope. Changes that this patch introduces: - You need to leave the v8::TryCatch scope around the bottom-most call to reset the termination state, in order to resume. - Explicitly check for termination exception and reporting it through the DevTools protocol after Runtime.evaluate and Debugger.evaluateOnCallFrame. Bug: v8:8455 Change-Id: I1f36f7a365985469813c2619bf16f18ee69aa4b8 Reviewed-on: https://chromium-review.googlesource.com/c/1337582Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#57963}
-
Michael Starzinger authored
The placement of the exceptipon section is by now restricted to be in between the Global and the Import section. This changes our validation to check this stricter requirement now. R=clemensh@chromium.org TEST=unittests/WasmModuleVerifyTest BUG=v8:8091 Change-Id: Ib3ea625fd4df93bffda47ced09e6969159f7ac70 Reviewed-on: https://chromium-review.googlesource.com/c/1356504Reviewed-by:
-
Predrag Rudic authored
64-bit implementations of ExtractBits and InsertBits were using 32-bit instructions. Masking when representation of instruction is 64 is now correct. Also added optimization for 32-bit InsertBits. Change-Id: I3d5117835daa67708e544d01d1d9058dcc0cc64e Reviewed-on: https://chromium-review.googlesource.com/c/1355141Reviewed-by:
Sreten Kovacevic <skovacevic@wavecomp.com> Commit-Queue: Sreten Kovacevic <skovacevic@wavecomp.com> Cr-Commit-Position: refs/heads/master@{#57961}
-
Clemens Hammacher authored
Building on linux x64 with "is_component_build = true" currently fails with linker errors (undefined references). This CL fixes that. R=ahaas@chromium.org TBR=mseaborn@chromium.org,mark@chromium.org Bug: v8:8532 Change-Id: I6b32c00bd974a22268ad1f161ce06a9ebe47c805 Reviewed-on: https://chromium-review.googlesource.com/c/1356505Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57960}
-
Camillo Bruni authored
Make sure that the testAddFn is always optimized. Bug: v8:8220 Change-Id: I38543dc4cf99df6a379c9474ce275af2c9ef015d Reviewed-on: https://chromium-review.googlesource.com/c/1355401 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#57959}
-
Clemens Hammacher authored
Minor refactoring. R=titzer@chromium.org Bug: v8:8238 Change-Id: Ibf3388cf8fc4a8d618e2e0da53209e29e753058d Reviewed-on: https://chromium-review.googlesource.com/c/1356501Reviewed-by:
-
Toon Verwaest authored
Move from ParseAndClassifyIdentifier to places where we either know that what we're parsing are parameters, or where they could become (async) arrow formals. Change-Id: Ic69bb586ed29ba9ac7b4dbef5d11a2e1954e7332 Reviewed-on: https://chromium-review.googlesource.com/c/1356503Reviewed-by:
-
Peter Marshall authored
This reverts commit 4e3a17d0. Reason for revert: Web compact issues, see crbug.com/910252 Original change's description: > [runtime] Reduce spread/apply call max arguments > > Bug: chromium:906043 > Change-Id: I308b29af0644c318d73926b27e65a94913c760c7 > Reviewed-on: https://chromium-review.googlesource.com/c/1346115 > Commit-Queue: Peter Marshall <petermarshall@chromium.org> > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57731} TBR=jarin@chromium.org,jgruber@chromium.org,petermarshall@chromium.org,bmeurer@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: chromium:906043 Change-Id: I240c1b55c10fd3e108e3c49f93ce1d9ca9c61780 Reviewed-on: https://chromium-review.googlesource.com/c/1356502Reviewed-by:
-
Tao Pan authored
In the case of using start and size to manage range, the range is start ~ start + size - 1, start + size is out of the range. The template function IsInRange(T value, U lower_limit, U higher_limit) judge whether value is in the range lower_limit ~ higher_limit. IsInRange(pc, start, start + isolate->embedded_blob_size()) misjudge the case pc == start + isolate->embedded_blob_size() Signed-off-by:
Tao Pan <tao.pan@intel.com> Change-Id: Iad172454bacb27a1328bbdda5863d28c9853a6db Bug: v8:8530 Change-Id: Iad172454bacb27a1328bbdda5863d28c9853a6db Reviewed-on: https://chromium-review.googlesource.com/c/1355633Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/b7e2add..e066ef7 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/eee0f6a..63d69d7 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/44d4b29..dd53081 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/8a671fe..5422fce Rolling v8/tools/luci-go:infra/tools/luci/isolate/${platform}: https://chrome-infra-packages.appspot.com/infra/tools/luci/isolate/${platform}/+log/git_rev..git_rev TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I4c5055d0a46a6ab5b0f4f30a70520d172ca77bd3 Reviewed-on: https://chromium-review.googlesource.com/c/1355632Reviewed-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@{#57954}
-
Aseem Garg authored
This is a reland of 9436e8a8 This CL simplifies the wasm/futex.js test so that it doesn't push the limits of d8. Original change's description: > [wasm] Add I64AtomicWait implementation > > Bug=v8:8075 > R=adamk@chromium.org,binji@chromium.org > > Change-Id: I11ef5daccd043123b23e60c93ee0df79cabe9ccd > Reviewed-on: https://chromium-review.googlesource.com/c/1342948 > Reviewed-by: Adam Klein <adamk@chromium.org> > Reviewed-by: Ben Smith <binji@chromium.org> > Commit-Queue: Aseem Garg <aseemgarg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#57917} Change-Id: Ifd26f1ecdb9fe24a1896162bb4d4285f9188a9ba Reviewed-on: https://chromium-review.googlesource.com/c/1351304 Commit-Queue: Aseem Garg <aseemgarg@chromium.org> Reviewed-by:
Ben Smith <binji@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#57953}
-
Jakob Kummerow authored
Bug: v8:3770 Change-Id: I6ad84a663926fffc9e1acc590c13780c39461274 Reviewed-on: https://chromium-review.googlesource.com/c/1351248 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Reviewed-by:
-
- 29 Nov, 2018 9 commits
-
-
Ben Smith authored
The bulk-memory proposal adds a new DataCount section that declares the number of data segments that are expected to be seen in the Data section. This is similar to the way the number of functions is split between the Function and Code sections. The DataCount section occurs before the Code section, so we can do single-pass validation of the new `memory.init` and `memory.drop` instructions, which have data segment indices as immediates. Bug: v8:7747 Change-Id: Ibc5a7ee9336dbc5d0fd667572c42cb065c048e00 Reviewed-on: https://chromium-review.googlesource.com/c/1352792 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by:
-
Camillo Bruni authored
This should reduce the likelyhood of getting indistinguishable map log events with --trace-maps. Bug: v8:8524 Change-Id: I5dad7a026ec9384960177298afadc1f9fa710eda Reviewed-on: https://chromium-review.googlesource.com/c/1354890Reviewed-by:
-
Ben Smith authored
Make sure to check that the number of declared functions (specified in the function section) matches the number of function bodies, even if the code section is omitted. Note that it is valid to have a function section with zero declared functions and an omitted code section, and vice versa. Bug: v8:8514 Change-Id: I4effa5abe2ed6d71146a665d2df6a2f48b5a84be Reviewed-on: https://chromium-review.googlesource.com/c/1351306 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by:
-
Ben L. Titzer authored
This CL moves a number of memory-related methods out of utils into its own header, since utils.h is included in many places that do not need these methods. R=clemensh@chromium.org,mstarzinger@chromium.org Change-Id: I5155baf329844784286413408c05c7108b789020 Reviewed-on: https://chromium-review.googlesource.com/c/1354889 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Cr-Commit-Position: refs/heads/master@{#57948}
-
Andreas Haas authored
The problem were missing V8_EXPORT_PRIVATE and V8_EXPORT. The unittests test if the trap handler only handles those traps it is supposed to handle: * Only handle traps when the thread-in-wasm flag is set. * Only handle traps of the right type, i.e. memory access violations. * Only handle traps at recorded instructions. The tests also test the consistency of the thread-in-wasm flag. I made one change in the trap handler where that consistency could be violated. All tests are executed with the default trap handler provided by V8, and with the trap handler callback installed in a test signal/exception handler. Patchset 1 is the original CL. R=mstarzinger@chromium.org Change-Id: I172d94f24cdba4c3a1f7f344825b059dbb59da79 Reviewed-on: https://chromium-review.googlesource.com/c/1351024Reviewed-by:
-
Michael Lippautz authored
Fix two bugs: - Initial configuration of limit allowed to go below the size of already allocated objects. - Context disposal without dependend context reset the heap state to not configured without actually increasing the limit again. Bug: chromium:843903 Change-Id: Ibdcf69b0b92b800f8919d5cc98186334945d811f Reviewed-on: https://chromium-review.googlesource.com/c/1355143Reviewed-by:
-
Michael Starzinger authored
R=clemensh@chromium.org BUG=v8:8091 Change-Id: Ib0e0b50d1fe24b0e528a3dd9849829799b33f1bc Reviewed-on: https://chromium-review.googlesource.com/c/1355139Reviewed-by:
-
Clemens Hammacher authored
This adds error functions that receive offsets instead of pc, since the streaming compiler stores different sections in different buffers, so computing pointer differences between different sections does not work. We keep the pc-based methods for now to reduce code-churn and complexity at the different call sites. R=ahaas@chromium.org CC=binji@chromium.org Bug: v8:8238 Change-Id: I1aa68740bdda93c3341431aa7a81ac01ecfb71bb Reviewed-on: https://chromium-review.googlesource.com/c/1354463Reviewed-by:
-
Michael Starzinger authored
This introduces a dedicated instance type for exception tags. The main motivation is to reduce their footprint and getting rid of a temporary workaround that used the {JSObject} type for this purpose. R=clemensh@chromium.org BUG=v8:8091 Change-Id: Id5678bce513f2ac086c7380bd803011b11d5050e Reviewed-on: https://chromium-review.googlesource.com/c/1354464Reviewed-by:
-
