commit | 64b74dbd09477985c36f1f2416fc7694d089dc8c | [log] [tgz] |
---|---|---|
author | ysuzuki@apple.com <ysuzuki@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Tue Feb 05 06:32:08 2019 +0000 |
committer | ysuzuki@apple.com <ysuzuki@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Tue Feb 05 06:32:08 2019 +0000 |
tree | 600a395a715ddbdecb27579cb4988bed6ef5e888 | |
parent | 8e9ff32a6e08a72d23f3caa67e9f1540992ce994 [diff] |
[JSC] Shrink size of VM by lazily allocating IsoSubspaces for non-common types https://bugs.webkit.org/show_bug.cgi?id=193993 Reviewed by Keith Miller. Source/JavaScriptCore: JSC::VM has a lot of IsoSubspaces, and each takes 504B. This unnecessarily makes VM so large. And some of them are rarely used. We should allocate it lazily. In this patch, we make some `IsoSubspaces` `std::unique_ptr<IsoSubspace>`. And we add ensureXXXSpace functions which allocate IsoSubspaces lazily. This function is used by subspaceFor<> in each class. And we also add subspaceForConcurrently<> function, which is called from concurrent JIT tiers. This returns nullptr if the subspace is not allocated yet. JSCell::subspaceFor now takes second template parameter which tells the function whether subspaceFor is concurrently done. If the IsoSubspace is lazily created, we may return nullptr for the concurrent access. We ensure the space's initialization by using WTF::storeStoreFence when lazily allocating it. In GC's constraint solving, we may touch these lazily allocated spaces. At that time, we check the existence of the space before touching this. This is not racy because the main thread is stopped when the constraint solving is working. This changes sizeof(VM) from 64736 to 56472. Another interesting thing is that we removed `PreventCollectionScope preventCollectionScope(heap);` in `Subspace::initialize`. This is really dangerous API since it easily causes dead-lock between the collector and the mutator if IsoSubspace is dynamically created. We do want to make IsoSubspaces dynamically-created ones since the requirement of the pre-allocation poses a scalability problem of IsoSubspace adoption because IsoSubspace is large. Registered Subspace is only touched in the EndPhase, and the peripheries should be stopped when running EndPhase. Thus, as long as the main thread can run this IsoSubspace code, the collector is never EndPhase. So this is safe. * API/JSCallbackFunction.h: * API/ObjCCallbackFunction.h: (JSC::ObjCCallbackFunction::subspaceFor): * API/glib/JSCCallbackFunction.h: * CMakeLists.txt: * JavaScriptCore.xcodeproj/project.pbxproj: * bytecode/CodeBlock.cpp: (JSC::CodeBlock::visitChildren): (JSC::CodeBlock::finalizeUnconditionally): * bytecode/CodeBlock.h: * bytecode/EvalCodeBlock.h: * bytecode/ExecutableToCodeBlockEdge.h: * bytecode/FunctionCodeBlock.h: * bytecode/ModuleProgramCodeBlock.h: * bytecode/ProgramCodeBlock.h: * bytecode/UnlinkedFunctionExecutable.cpp: (JSC::UnlinkedFunctionExecutable::unlinkedCodeBlockFor): * bytecode/UnlinkedFunctionExecutable.h: * dfg/DFGSpeculativeJIT.cpp: (JSC::DFG::SpeculativeJIT::emitAllocateRawObject): (JSC::DFG::SpeculativeJIT::compileMakeRope): (JSC::DFG::SpeculativeJIT::compileNewObject): * ftl/FTLLowerDFGToB3.cpp: (JSC::FTL::DFG::LowerDFGToB3::compileMakeRope): (JSC::FTL::DFG::LowerDFGToB3::compileMaterializeNewObject): (JSC::FTL::DFG::LowerDFGToB3::allocateObject): (JSC::FTL::DFG::LowerDFGToB3::allocateVariableSizedObject): (JSC::FTL::DFG::LowerDFGToB3::allocateVariableSizedCell): * heap/Heap.cpp: (JSC::Heap::finalizeUnconditionalFinalizers): (JSC::Heap::deleteAllCodeBlocks): (JSC::Heap::deleteAllUnlinkedCodeBlocks): (JSC::Heap::addCoreConstraints): * heap/Subspace.cpp: (JSC::Subspace::initialize): * jit/AssemblyHelpers.h: (JSC::AssemblyHelpers::emitAllocateJSObjectWithKnownSize): (JSC::AssemblyHelpers::emitAllocateVariableSizedCell): * jit/JITOpcodes.cpp: (JSC::JIT::emit_op_new_object): * jit/JITOpcodes32_64.cpp: (JSC::JIT::emit_op_new_object): * runtime/DirectArguments.h: * runtime/DirectEvalExecutable.h: * runtime/ErrorInstance.h: (JSC::ErrorInstance::subspaceFor): * runtime/ExecutableBase.h: * runtime/FunctionExecutable.h: * runtime/IndirectEvalExecutable.h: * runtime/InferredValue.cpp: (JSC::InferredValue::visitChildren): * runtime/InferredValue.h: * runtime/InferredValueInlines.h: (JSC::InferredValue::finalizeUnconditionally): * runtime/InternalFunction.h: * runtime/JSAsyncFunction.h: * runtime/JSAsyncGeneratorFunction.h: * runtime/JSBoundFunction.h: * runtime/JSCell.h: (JSC::subspaceFor): (JSC::subspaceForConcurrently): * runtime/JSCellInlines.h: (JSC::allocatorForNonVirtualConcurrently): * runtime/JSCustomGetterSetterFunction.h: * runtime/JSDestructibleObject.h: * runtime/JSFunction.h: * runtime/JSGeneratorFunction.h: * runtime/JSImmutableButterfly.h: * runtime/JSLexicalEnvironment.h: (JSC::JSLexicalEnvironment::subspaceFor): * runtime/JSNativeStdFunction.h: * runtime/JSSegmentedVariableObject.h: * runtime/JSString.h: * runtime/ModuleProgramExecutable.h: * runtime/NativeExecutable.h: * runtime/ProgramExecutable.h: * runtime/PropertyMapHashTable.h: * runtime/ProxyRevoke.h: * runtime/ScopedArguments.h: * runtime/ScriptExecutable.cpp: (JSC::ScriptExecutable::clearCode): (JSC::ScriptExecutable::installCode): * runtime/Structure.h: * runtime/StructureRareData.h: * runtime/SubspaceAccess.h: Copied from Source/JavaScriptCore/runtime/InferredValueInlines.h. * runtime/VM.cpp: (JSC::VM::VM): * runtime/VM.h: (JSC::VM::SpaceAndSet::SpaceAndSet): (JSC::VM::SpaceAndSet::setFor): (JSC::VM::forEachScriptExecutableSpace): (JSC::VM::SpaceAndFinalizerSet::SpaceAndFinalizerSet): Deleted. (JSC::VM::SpaceAndFinalizerSet::finalizerSetFor): Deleted. (JSC::VM::ScriptExecutableSpaceAndSet::ScriptExecutableSpaceAndSet): Deleted. (JSC::VM::ScriptExecutableSpaceAndSet::clearableCodeSetFor): Deleted. (JSC::VM::UnlinkedFunctionExecutableSpaceAndSet::UnlinkedFunctionExecutableSpaceAndSet): Deleted. (JSC::VM::UnlinkedFunctionExecutableSpaceAndSet::clearableCodeSetFor): Deleted. * runtime/WeakMapImpl.h: (JSC::WeakMapImpl::subspaceFor): * wasm/js/JSWebAssemblyCodeBlock.h: * wasm/js/JSWebAssemblyMemory.h: * wasm/js/WebAssemblyFunction.h: * wasm/js/WebAssemblyWrapperFunction.h: Source/WebCore: * bindings/scripts/CodeGeneratorJS.pm: (GenerateHeader): * bridge/runtime_method.h: Source/WebKit: * WebProcess/Plugins/Netscape/JSNPMethod.h: * WebProcess/Plugins/Netscape/JSNPObject.h: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@240965 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git://git.webkit.org/WebKit.git WebKit
or
git clone https://git.webkit.org/git/WebKit.git WebKit
If you want to be able to commit changes to the repository, or just want to check out branches that aren’t contained in WebKit.git, you will need track WebKit's Subversion repository. You can run the following command to configure this and other options of the new Git clone for WebKit development.
Tools/Scripts/webkit-patch setup-git-clone
For information about this, and other aspects of using Git with WebKit, read the wiki page.
If you don‘t want to use Git, run the following command to check out WebKit’s Subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within Xcode.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
The first time after you install a new Xcode, you will need to run the following command to enable Xcode to build command line tools for iOS Simulator:
sudo Tools/Scripts/configure-xcode-for-ios-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for iOS:
Tools/Scripts/build-webkit --debug --ios-simulator.
For production builds:
cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/gtk/install-dependencies Tools/Scripts/update-webkitgtk-libs Tools/Scripts/build-webkit --gtk --debug
For more information on building WebKitGTK+, see the wiki page.
For production builds:
cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/wpe/install-dependencies Tools/Scripts/update-webkitwpe-libs Tools/Scripts/build-webkit --wpe --debug
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
If you have a development build, you can use the run-minibrowser script, e.g.:
run-minibrowser --debug --wpe
Pass one of --gtk
, --jsc-only
, or --wpe
to indicate the port to use.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.