commit | f2d16d749e1eb13ee39cabe1161b2b71d3a72aea | [log] [tgz] |
---|---|---|
author | mark.lam@apple.com <mark.lam@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Thu Oct 17 05:45:58 2019 +0000 |
committer | mark.lam@apple.com <mark.lam@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Thu Oct 17 05:45:58 2019 +0000 |
tree | 022b736ad89328ac5442d62dd344bfe22db13273 | |
parent | ff9c6e48f3add2399713e28a9d952b7902b9cd58 [diff] |
Reduce the amount of memory needed to store Options. https://bugs.webkit.org/show_bug.cgi?id=202105 Reviewed by Yusuke Suzuki. The size of the JSC::Config needed to store the Options is now reduced to 4K instead of 16K, enabled by constexpr template magic. 1. Instead of all options in a large array of OptionEntry (which is a union of all the option types), we now have separate arrays for each of the types of options. For example, Removed g_jscConfig.options[]. Added g_jscConfig.typeBoolOptions[]. Added g_jscConfig.typeInt32Options[]. Added g_jscConfig.typeDoubleOptions[]. ... We used to find the storage for the option using g_jscConfig.options[Options::ID]. We now find the storage for each type of option using g_jscConfig.options[optionTypeSpecificIndex<OptionTypeID, OptionID>()]. For example, Options::useJIT() used to be implemented as: inline bool& Options::useJIT() { return g_jscConfig.options[Options::useJITID]; } ... which is now replaced with: inline bool& Options::useJIT() { return g_jscConfig.typeBoolOptions[optionTypeSpecificIndex<OptionTypeID::Bool, OptionID::useJIT>()]; } MSVC has a bug where it cannot handle very large source files: see https://developercommunity.visualstudio.com/content/problem/653301/fatal-error-c1002-compiler-is-out-of-heap-space-in.html. This bug prevents this patch from building on MSVC. To workaround this bug, we don't inline the Options accessors when COMPILER(MSVC). This prevents MSVC from having to parse the large body of template code code to used to implement the inline accessors in every file that #include "Options.h". Also add the @no-unify attribute to Options.cpp (where we put the accessors) so that it doesn't trigger the MSVC bug also. 2. Introduce the optionTypeSpecificIndex() constexpr template function for computing the index of each option in their respective type specific options array. 3. Introduce OptionTypes, OptionTypeID, and OptionID. The OptionTypes namespace replaces OptionEntry as the container of option types. The OptionID enum class replaces Options::ID. The OptionTypeID enum class is new and is used together with OptionID in constexpr templates to compute the typeSpecificIndex of options. 4. Removed the OptionEntry struct and OptionEntry.h. After (1), this struct is only used in the Option class. We just moved the union of option types (that OptionEntry embeds) into the Option class. Moved class OptionRange into OptionsList.h. 5. Removed the large OptionEntry arrays from JSC::Config. Added type specific options arrays. Also ordered these arrays to maximize compactness and minimize internal fragmentation. 6. Changed scaleJITPolicy() to go directly to g_jscConfig.typeInt32Options[] instead of going through the Option wrapper object. This allows us to simplify things and make the Option class a read only interface of options. 7. Changed Options::initialize() to only compute the option default value once. The default value specified in the OptionsList may not always be a constant. Sometimes, it is a function call. 8. The Option class now only gives read only access to the options. The Option class' role is to provide an interface for reading an option at any given OptionID without first knowing about the type of the specific option. It is useful for iterating options, and is currently only used by Options::dumpOption(). Technically, we could merge all the Option class code into its single client. We opted not to do this because the amount of code is non-trivial, and the Option class does a good job of encapsulating this functionality. * API/glib/JSCOptions.cpp: (jscOptionsSetValue): (jscOptionsGetValue): (jsc_options_foreach): (jsc_options_get_option_group): * CMakeLists.txt: * JavaScriptCore.xcodeproj/project.pbxproj: * Sources.txt: * runtime/JSCConfig.h: * runtime/OptionEntry.h: Removed. * runtime/Options.cpp: (JSC::Options::isAvailable): (JSC::overrideOptionWithHeuristic): (JSC::optionTypeSpecificIndex): (JSC::scaleJITPolicy): (JSC::recomputeDependentOptions): (JSC::Options::initialize): (JSC::Options::setOptionWithoutAlias): (JSC::Options::dumpAllOptions): (JSC::Options::dumpOption): (JSC::Option::Option): (JSC::Option::defaultOption const): (JSC::Option::dump const): (JSC::Option::operator== const): * runtime/Options.h: (JSC::Option::id const): (JSC::Option::name const): (JSC::Option::description const): (JSC::Option::type const): (JSC::Option::availability const): (JSC::Option::isOverridden const): (JSC::Option::Option): (JSC::Option::idIndex const): (JSC::optionTypeSpecificIndex): (JSC::Option::defaultOption const): Deleted. (JSC::Option::boolVal): Deleted. (JSC::Option::unsignedVal): Deleted. (JSC::Option::doubleVal): Deleted. (JSC::Option::int32Val): Deleted. (JSC::Option::optionRangeVal): Deleted. (JSC::Option::optionStringVal): Deleted. (JSC::Option::gcLogLevelVal): Deleted. * runtime/OptionsList.h: (JSC::OptionRange::operator= ): (JSC::OptionRange::rangeString const): (JSC::countNumberOfJSCOptionsOfType): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@251226 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.