Skip to content

/ChakraCore

ChakraCore is the core part of the Chakra JavaScript engine that powers Microsoft Edge
chakracore javascript-engine jsrt microsoft vm javascript js runtime windows linux chakra osx help-wanted up-for-grabs cplusplus-11 cplusplus mit-license
JavaScript C++ WebAssembly Objective-C C Assembly Other
  1. JavaScript 51.9%
  2. C++ 39.8%
  3. WebAssembly 3.2%
  4. Objective-C 2.5%
  5. C 1.7%
  6. Assembly 0.2%
  7. Other 0.7%
Branch: master
Find File
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Download ZIP

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching Xcode...

If nothing happens, download Xcode and try again.

Launching Visual Studio...

If nothing happens, download the GitHub extension for Visual Studio and try again.

Kevin Smith
Kevin Smith [MERGE #6247 @zenparsing] Insert a ByteCodeUses instr for arguments w… 
…hen inlining apply target

Merge pull request #6247 from zenparsing:inline-apply-target-bug

When inline apply target optimization is used for:

```js
inlinee.apply(obj, arguments);
```

a bailout will occur if the target function is not the expected inlinee. When this occurs, the arguments object needs to be created for use in the interpreter. Currently, GlobOpt is not correctly tracking that the arguments object symbol is needed by the interpreter, and the arguments object is not getting added to the associated bailout info.

This PR adds a `ByteCodeUses` instr for this inlining case.

Additional changes:

- Explicit initialization for the `m_nonEscapingArgObjAlias` field of StackSym.
- `Src2` is no longer used for `BytecodeArgOutUse` (GlobOpt was not checking Src2)
Latest commit 8fcb0f1 Aug 17, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Build add ChakraCoreWindows.h to nuget include path Jun 17, 2019
bin [MERGE #6226 @nhat-nguyen] Enable globopt for generator functions Aug 12, 2019
deps/Chakra.ICU Update Chakra.ICU to support ICU 62.1 Aug 28, 2018
jenkins Fix EOL violations introduced by commits that came into master via a … Feb 28, 2019
lib [MERGE #6247 @zenparsing] Insert a ByteCodeUses instr for arguments w… Aug 16, 2019
manifests [1.11>master] [1.10>1.11] [MERGE #5787 @Cellule] Merge changes from W… Oct 23, 2018
pal add PAL guid file Feb 1, 2019
test Insert a ByteCodeUses instr for arguments when inlining apply target Aug 15, 2019
tools add support for vs2019 May 17, 2019
.gitattributes Revert "Update .gitattributes" Dec 21, 2017
.gitignore Add ClangCL VcBuild directory to gitignore Jul 18, 2018
BUILD.gn fix copyright headers Jan 30, 2019
CMakeLists.txt Add ccache option to CMakeLists.txt and build.sh Mar 14, 2018
CONTRIBUTING.md Update CONTRIBUTING.md Feb 25, 2019
LICENSE.txt LICENSE: Remove project name from line 1 Nov 28, 2017
README.md updated ADO badges Jul 19, 2019
RegenAllByteCode.cmd Implement the prototype of JS built in Array.prototype.indexOf Nov 3, 2017
RegenAllByteCodeNoBuild.cmd Remove duplicate bytecode generation Aug 13, 2018
THIRD-PARTY-NOTICES.txt add third party notice May 7, 2018
build.sh Update the ICU download URLs to GitHub locations. Also, update to ICU… Apr 25, 2019
netci.groovy [1.11>master] [1.10>1.11] [MERGE #5758 @sethbrenith] Use different ma… Oct 5, 2018

README.md

ChakraCore

Join the chat at https://gitter.im/Microsoft/ChakraCore Licensed under the MIT License PR's Welcome

ChakraCore is the core part of Chakra, the high-performance JavaScript engine that powers Microsoft Edge and Windows applications written in HTML/CSS/JS. ChakraCore supports Just-in-time (JIT) compilation of JavaScript for x86/x64/ARM, garbage collection, and a wide range of the latest JavaScript features. ChakraCore also supports the JavaScript Runtime (JSRT) APIs, which allows you to easily embed ChakraCore in your applications.

You can stay up-to-date on progress by following the MSEdge developer blog.

Build Status

Debug Test Release
Windows 10 (x64) Build Status Build Status Build Status
Windows 10 (x86) Build Status Build Status Build Status
Windows 10 (ARM) Build Status Build Status Build Status
Windows 10 (ARM64) Build Status Build Status Build Status
Ubuntu 16.04 (x64)[a] Build Status Build Status Build Status
Ubuntu 16.04 (x64)[s] Build Status Build Status Build Status
Ubuntu 16.04 (x64)[s][n] * Build Status *
macOS 10.13 (x64)[a] Build Status Build Status Build Status
macOS 10.13 (x64)[s][n] * Build Status *

[a] Static | [s] Shared | [n] NoJIT | * Omitted

Above is a table of our rolling build status. We run additional builds on a daily basis. See Build Status for the status of all builds and additional details.

Security

If you believe you have found a security issue in ChakraCore, please share it with us privately following the guidance at the Microsoft Security TechCenter. Reporting it via this channel helps minimize risk to projects built with ChakraCore.

Documentation

Building ChakraCore

You can build ChakraCore on Windows 7 SP1 or above, and Windows Server 2008 R2 or above, with either Visual Studio 2015 or 2017 with C++ support installed. Once you have Visual Studio installed:

  • Clone ChakraCore through git clone https://github.com/Microsoft/ChakraCore.git
  • Open Build\Chakra.Core.sln in Visual Studio
  • Build Solution

More details in Building ChakraCore.

Alternatively, see Getting ChakraCore binaries for pre-built ChakraCore binaries.

Using ChakraCore

Once built, you have a few options for how you can use ChakraCore:

  • The most basic is to test the engine is running correctly with the ch.exe binary. This app is a lightweight hosting of JSRT that you can use to run small applications. After building, you can find this binary in:
    • Build\VcBuild\bin\${platform}_${configuration}
    • (e.g. Build\VcBuild\bin\x64_debug)
  • You can embed ChakraCore in your applications - see documentation and samples.
  • Finally, you can also use ChakraCore as the JavaScript engine in Node. You can learn more by reading how to use Chakra as Node's JS engine

A note about using ChakraCore: ChakraCore is the foundational JavaScript engine, but it does not include the external APIs that make up the modern JavaScript development experience. For example, DOM APIs like document.write() are additional APIs that are not available by default and would need to be provided. For debugging, you may instead want to use print().

Contribute

Contributions to ChakraCore are welcome. Here is how you can contribute to ChakraCore:

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Please refer to Contribution Guidelines for more details.

License

Code licensed under the MIT License.

Roadmap

For details on our planned features and future direction please refer to our Roadmap.

Contact Us

If you have questions about ChakraCore, or you would like to reach out to us about an issue you're having or for development advice as you work on a ChakraCore issue, you can reach us as follows:

  • Open an issue and prefix the issue title with [Question]. See Question tag for already-opened questions.
  • Discuss ChakraCore with the team and the community on our Gitter Channel.
  • You can also start private messages with individual ChakraCore developers via Gitter.
You can’t perform that action at this time.