commit | b82f084a00fbd4fab443d5fa3857bc2fbeab0216 | [log] [tgz] |
---|---|---|
author | fpizlo@apple.com <fpizlo@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Dec 13 02:35:54 2017 +0000 |
committer | fpizlo@apple.com <fpizlo@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Dec 13 02:35:54 2017 +0000 |
tree | d46d91dc8c015a4ff1d9a07ea2e24ec21e4771b4 | |
parent | 786b6a5b1d17c0e3cc2757dd99bded840614b7df [diff] |
It should be possible to flag a cell for unconditional finalization https://bugs.webkit.org/show_bug.cgi?id=180636 Reviewed by Saam Barati. Source/JavaScriptCore: UnconditionalFinalizers were annoying - you had to allocate them and you had to manage a global linked list - but they had some nice properties: - You only did the hardest work (creating the UnconditionalFinalizer) on first GC where you survived and needed it. -> Just needing it wasn't enough. -> Just surviving wasn't enough. The new API based on IsoSubspaces meant that just surviving was enough to cause unconditional finalizer logic to be invoked. I think that's not great. InferredType got around this by making InferredStructure a cell, but this was a gross hack. For one, it meant that InferredStructure would survive during the GC in which its finalizer obviated the need for its existence. It's not really an idiom I want us to repeat because it sounds like the sort of thing that turns out to be subtly broken. We really need to have a way of indicating when you have entered into the state that requires your unconditional finalizer to be invoked. Basically, we want to be able to track the set of objects that need unconditional finalizers. Only the subset of that set that overlaps with the set of marked objects needs to be accurate. The easiest way to do this is a hierarchy of bitvectors: one to say which MarkedBlocks have objects that have unconditional finalizers, and another level to say which atoms within a MarkedBlock have unconditional finalizers. This change introduces IsoCellSet, which couples itself to the MarkedAllocator of some IsoSubspace to allow maintaining a set of objects (well, cells - you could do this with auxiliaries) that belong to that IsoSubspace. It'll have undefined behavior if you try to add/remove/contains an object that isn't in that IsoSubspace. For objects in that subspace, you can add/remove/contains and forEachMarkedCell. The cost of each IsoCellSet is at worst about 0.8% increase in size to every object in the subspace that the set is attached to. So, it makes sense to have a handful per subspace max. This change only needs one per subspace, but you could imagine more if we do this for WeakReferenceHarvester. To absolutely minimize the possibility that this incurs costs, the add/remove/contains functions can be used from any thread so long as forEachMarkedCell isn't running. This means that InferredType only needs to add itself to the set during visitChildren. Thus, it needs to both survive and need it for the hardest work to take place. The work of adding does involve a gnarly load chain that ends in a CAS: load block handle from block, load index, load segment, load bitvector, load bit -> if not set, then CAS. That's five dependent loads! However, it's perfect for running in parallel since the only write operations are to widely dispersed cache lines that contain the bits underlying the set. The best part is how forEachMarkedCell works. That skips blocks that don't have any objects that need unconditional finalizers, and only touches the memory of marked objects that have the unconditional finalizer bit set. It will walk those objects in roughly address order. I previously found that this speeds up walking over a lot of objects when I made similar changes for DOM GC (calling visitAdditionalChildren via forEachMarkedCell rather than by walking a HashSet). This change makes InferredStructure be a malloc object again, but now it's in an IsoHeap. My expectation for this change is that it's perf-neutral. Long-term, it gives us a path forward for eliminating UnconditionalFinalizer and WeakReferenceHarvester while using IsoSubspace in more places. * JavaScriptCore.xcodeproj/project.pbxproj: * Sources.txt: * heap/AtomIndices.h: Added. (JSC::AtomIndices::AtomIndices): * heap/Heap.cpp: (JSC::Heap::finalizeUnconditionalFinalizers): * heap/Heap.h: * heap/IsoCellSet.cpp: Added. (JSC::IsoCellSet::IsoCellSet): (JSC::IsoCellSet::~IsoCellSet): (JSC::IsoCellSet::addSlow): (JSC::IsoCellSet::didResizeBits): (JSC::IsoCellSet::didRemoveBlock): (JSC::IsoCellSet::sweepToFreeList): * heap/IsoCellSet.h: Added. * heap/IsoCellSetInlines.h: Added. (JSC::IsoCellSet::add): (JSC::IsoCellSet::remove): (JSC::IsoCellSet::contains const): (JSC::IsoCellSet::forEachMarkedCell): * heap/IsoSubspace.cpp: (JSC::IsoSubspace::didResizeBits): (JSC::IsoSubspace::didRemoveBlock): (JSC::IsoSubspace::didBeginSweepingToFreeList): * heap/IsoSubspace.h: * heap/MarkedAllocator.cpp: (JSC::MarkedAllocator::addBlock): (JSC::MarkedAllocator::removeBlock): * heap/MarkedAllocator.h: * heap/MarkedAllocatorInlines.h: * heap/MarkedBlock.cpp: (JSC::MarkedBlock::Handle::sweep): (JSC::MarkedBlock::Handle::isEmpty): Deleted. * heap/MarkedBlock.h: (JSC::MarkedBlock::marks const): (JSC::MarkedBlock::Handle::newlyAllocated const): * heap/MarkedBlockInlines.h: (JSC::MarkedBlock::Handle::isAllocated): (JSC::MarkedBlock::Handle::isEmpty): (JSC::MarkedBlock::Handle::emptyMode): (JSC::MarkedBlock::Handle::forEachMarkedCell): * heap/Subspace.cpp: (JSC::Subspace::didResizeBits): (JSC::Subspace::didRemoveBlock): (JSC::Subspace::didBeginSweepingToFreeList): * heap/Subspace.h: * heap/SubspaceInlines.h: (JSC::Subspace::forEachMarkedCell): * runtime/InferredStructure.cpp: (JSC::InferredStructure::InferredStructure): (JSC::InferredStructure::create): Deleted. (JSC::InferredStructure::destroy): Deleted. (JSC::InferredStructure::createStructure): Deleted. (JSC::InferredStructure::visitChildren): Deleted. (JSC::InferredStructure::finalizeUnconditionally): Deleted. (JSC::InferredStructure::finishCreation): Deleted. * runtime/InferredStructure.h: * runtime/InferredStructureWatchpoint.cpp: (JSC::InferredStructureWatchpoint::fireInternal): * runtime/InferredType.cpp: (JSC::InferredType::visitChildren): (JSC::InferredType::willStoreValueSlow): (JSC::InferredType::makeTopSlow): (JSC::InferredType::set): (JSC::InferredType::removeStructure): (JSC::InferredType::finalizeUnconditionally): * runtime/InferredType.h: * runtime/VM.cpp: (JSC::VM::VM): * runtime/VM.h: Source/WTF: This adds ConcurrentVector, which is like SegmentedVector, but wastes some space to allow resizing to proceed concurrently to access. It's not possible to resize concurrently to resizing, concurrent read/writes aren't protected from racing if they access the same element, and who knows what you'll get if you iterate up to size() while someone else append()s. The key insight is to stash all prior copies of the spine, so that nobody crashes trying to access a stale spine. I'm going to want to do the same thing for FastBitVector, by creating a segmented WordOwner class. That would require repeating the dance of having a spine that can resize while stashing old versions. So, the spine resizing logic is abstracted behind ConcurrentBuffer. You could use that as a kind of "concurrent vector" for immutable data. That's how ConcurrentVector uses it: it's an immutable array of segment pointers. * WTF.xcodeproj/project.pbxproj: * wtf/ConcurrentBuffer.h: Added. (WTF::ConcurrentBuffer::ConcurrentBuffer): (WTF::ConcurrentBuffer::~ConcurrentBuffer): (WTF::ConcurrentBuffer::growExact): (WTF::ConcurrentBuffer::grow): (WTF::ConcurrentBuffer::array const): (WTF::ConcurrentBuffer::operator[]): (WTF::ConcurrentBuffer::operator[] const): (WTF::ConcurrentBuffer::createArray): * wtf/ConcurrentVector.h: Added. (WTF::ConcurrentVectorIterator::~ConcurrentVectorIterator): (WTF::ConcurrentVectorIterator::operator* const): (WTF::ConcurrentVectorIterator::operator-> const): (WTF::ConcurrentVectorIterator::operator++): (WTF::ConcurrentVectorIterator::operator== const): (WTF::ConcurrentVectorIterator::operator!= const): (WTF::ConcurrentVectorIterator::operator=): (WTF::ConcurrentVectorIterator::ConcurrentVectorIterator): (WTF::ConcurrentVector::~ConcurrentVector): (WTF::ConcurrentVector::size const): (WTF::ConcurrentVector::isEmpty const): (WTF::ConcurrentVector::at): (WTF::ConcurrentVector::at const): (WTF::ConcurrentVector::operator[]): (WTF::ConcurrentVector::operator[] const): (WTF::ConcurrentVector::first): (WTF::ConcurrentVector::first const): (WTF::ConcurrentVector::last): (WTF::ConcurrentVector::last const): (WTF::ConcurrentVector::takeLast): (WTF::ConcurrentVector::append): (WTF::ConcurrentVector::alloc): (WTF::ConcurrentVector::removeLast): (WTF::ConcurrentVector::grow): (WTF::ConcurrentVector::begin): (WTF::ConcurrentVector::end): (WTF::ConcurrentVector::segmentExistsFor): (WTF::ConcurrentVector::segmentFor): (WTF::ConcurrentVector::subscriptFor): (WTF::ConcurrentVector::ensureSegmentsFor): (WTF::ConcurrentVector::ensureSegment): (WTF::ConcurrentVector::allocateSegment): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@225831 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.
Downloading Safari Technology Preview to test the latest version of WebKit.
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
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.
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 WebKit.
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.
Install the dependencies by running the following command:
Tools/gtk/install-dependencies
Then run the following command to build additional dependencies:
Tools/Scripts/update-webkitgtk-libs
Run the following command to build WebKit with debugging symbols for GTK+ port:
Tools/Scripts/build-webkit --debug --gtk
Note that the procedure for building a release tarball is different. For more information, see the wiki page.
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
.
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.