commit | fcab24fd59da822694f262117277cbfbefe57af4 | [log] [tgz] |
---|---|---|
author | utatane.tea@gmail.com <utatane.tea@gmail.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Sep 27 18:51:12 2017 +0000 |
committer | utatane.tea@gmail.com <utatane.tea@gmail.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Sep 27 18:51:12 2017 +0000 |
tree | 19e7bef11305ed13e3d8f30c8231d5dda7105b5c | |
parent | e24c6ad6788eea2e3d03523501f9630b766c32f6 [diff] |
Add Above/Below comparisons for UInt32 patterns https://bugs.webkit.org/show_bug.cgi?id=177281 Reviewed by Saam Barati. JSTests: * stress/uint32-comparison-jump.js: Added. (shouldBe): (above): (aboveOrEqual): (below): (belowOrEqual): (notAbove): (notAboveOrEqual): (notBelow): (notBelowOrEqual): * stress/uint32-comparison.js: Added. (shouldBe): (above): (aboveOrEqual): (below): (belowOrEqual): (aboveTest): (aboveOrEqualTest): (belowTest): (belowOrEqualTest): Source/JavaScriptCore: Sometimes, we would like to have UInt32 operations in JS. While VM does not support UInt32 nicely, VM supports efficient Int32 operations. As long as signedness does not matter, we can just perform Int32 operations instead and recognize its bit pattern as UInt32. But of course, some operations respect signedness. The most frequently used one is comparison. Octane/zlib performs UInt32 comparison by performing `val >>> 0`. It emits op_urshift and op_unsigned. op_urshift produces UInt32 in Int32 form. And op_unsigned will generate Double value if the generated Int32 is < 0 (which should be UInt32). There is a chance for optimization. The given code pattern is the following. op_unsigned(op_urshift(@1)) lessThan:< op_unsigned(op_urshift(@2)) This can be converted to the following. op_urshift(@1) below:< op_urshift(@2) The above conversion is nice since 1. We can avoid op_unsigned. This could be unsignedness check in DFG. Since this check depends on the value of Int32, dropping this check is not as easy as removing Int32 edge filters. 2. We can perform unsigned comparison in Int32 form. We do not need to convert them to DoubleRep. Since the above comparison exists in Octane/zlib's *super* hot path, dropping op_unsigned offers huge win. At first, my patch attempts to convert the above thing in DFG pipeline. However it poses several problems. 1. MovHint is not well removed. It makes UInt32ToNumber (which is for op_unsigned) live. 2. UInt32ToNumber could cause an OSR exit. So if we have the following nodes, 2: UInt32ToNumber(@0) 3: MovHint(@2, xxx) 4: UInt32ToNumber(@1) 5: MovHint(@1, xxx) we could drop @5's MovHint. But @3 is difficult since @4 can exit. So, instead, we start introducing a simple optimization in the bytecode compiler. It performs pattern matching for op_urshift and comparison to drop op_unsigned. We adds op_below and op_above families to bytecodes. They only accept Int32 and perform unsigned comparison. This offers 4% performance improvement in Octane/zlib. baseline patched zlib x2 431.07483+-16.28434 414.33407+-9.38375 might be 1.0404x faster * bytecode/BytecodeDumper.cpp: (JSC::BytecodeDumper<Block>::printCompareJump): (JSC::BytecodeDumper<Block>::dumpBytecode): * bytecode/BytecodeDumper.h: * bytecode/BytecodeList.json: * bytecode/BytecodeUseDef.h: (JSC::computeUsesForBytecodeOffset): (JSC::computeDefsForBytecodeOffset): * bytecode/Opcode.h: (JSC::isBranch): * bytecode/PreciseJumpTargetsInlines.h: (JSC::extractStoredJumpTargetsForBytecodeOffset): * bytecompiler/BytecodeGenerator.cpp: (JSC::BytecodeGenerator::emitJumpIfTrue): (JSC::BytecodeGenerator::emitJumpIfFalse): * bytecompiler/NodesCodegen.cpp: (JSC::BinaryOpNode::emitBytecode): * dfg/DFGAbstractInterpreterInlines.h: (JSC::DFG::AbstractInterpreter<AbstractStateType>::executeEffects): * dfg/DFGByteCodeParser.cpp: (JSC::DFG::ByteCodeParser::parseBlock): * dfg/DFGCapabilities.cpp: (JSC::DFG::capabilityLevel): * dfg/DFGClobberize.h: (JSC::DFG::clobberize): * dfg/DFGDoesGC.cpp: (JSC::DFG::doesGC): * dfg/DFGFixupPhase.cpp: (JSC::DFG::FixupPhase::fixupNode): * dfg/DFGIntegerRangeOptimizationPhase.cpp: * dfg/DFGNodeType.h: * dfg/DFGPredictionPropagationPhase.cpp: * dfg/DFGSafeToExecute.h: (JSC::DFG::safeToExecute): * dfg/DFGSpeculativeJIT.cpp: (JSC::DFG::SpeculativeJIT::compileCompareUnsigned): * dfg/DFGSpeculativeJIT.h: * dfg/DFGSpeculativeJIT32_64.cpp: (JSC::DFG::SpeculativeJIT::compile): * dfg/DFGSpeculativeJIT64.cpp: (JSC::DFG::SpeculativeJIT::compile): * dfg/DFGStrengthReductionPhase.cpp: (JSC::DFG::StrengthReductionPhase::handleNode): * dfg/DFGValidate.cpp: * ftl/FTLCapabilities.cpp: (JSC::FTL::canCompile): * ftl/FTLLowerDFGToB3.cpp: (JSC::FTL::DFG::LowerDFGToB3::compileNode): (JSC::FTL::DFG::LowerDFGToB3::compileCompareBelow): (JSC::FTL::DFG::LowerDFGToB3::compileCompareBelowEq): * jit/JIT.cpp: (JSC::JIT::privateCompileMainPass): * jit/JIT.h: * jit/JITArithmetic.cpp: (JSC::JIT::emit_op_below): (JSC::JIT::emit_op_beloweq): (JSC::JIT::emit_op_jbelow): (JSC::JIT::emit_op_jbeloweq): (JSC::JIT::emit_compareUnsignedAndJump): (JSC::JIT::emit_compareUnsigned): * jit/JITArithmetic32_64.cpp: (JSC::JIT::emit_compareUnsignedAndJump): (JSC::JIT::emit_compareUnsigned): * llint/LowLevelInterpreter.asm: * llint/LowLevelInterpreter32_64.asm: * llint/LowLevelInterpreter64.asm: * parser/Nodes.h: (JSC::ExpressionNode::isBinaryOpNode const): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@222564 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.