You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Marc Poulhiès 0f65266d60 WIP: sample doc for RISCV 3 years ago
.github Add title placeholder for issue templates 4 years ago
.idea Fix up handling of error indicators. Fixes #1384 4 years ago
docs append to documentation 3 years ago
etc Merge pull request #1643 from mattgodbolt/features/cdn 3 years ago
examples * Add Python support (#1612) 3 years ago
lib WIP: sample doc for RISCV 3 years ago
static WIP for generic doc 3 years ago
test WIP for generic doc 3 years ago
views Merge pull request #1643 from mattgodbolt/features/cdn 3 years ago
.eslintignore Remove c-preload compiler wrapper in favour of firejail. See #429 4 years ago
.eslintrc Configurable environment passthrough. 3 years ago
.gitattributes Attempt two at specifying linguist config 5 years ago
.gitignore Support serving static content externally 3 years ago
.istanbul.yml Replace restreamer with a custom proxy handler that works for us. Fixes #1289 4 years ago
.travis.yml revert back the original 3 years ago
AUTHORS.md Update documentation 4 years ago
CODEOWNERS Improve small details 5 years ago
CODE_OF_CONDUCT.md Improve docs (Wording & raw and stylized visuals) 5 years ago
CONTRIBUTING.md Support Visual C++ and Windows well 5 years ago
CONTRIBUTORS.md * Add Python support (#1612) 3 years ago
LICENSE More license shenanigans 3 years ago
Makefile Support serving static content externally 3 years ago
PULL_REQUEST_TEMPLATE.md Fix PULL_REQUEST_TEMPLATE.md comment tag 5 years ago
README.md Update Roadmap and README 3 years ago
Roadmap.md Update Roadmap and README 3 years ago
app.build.js Don't attempt to pack monaco-editor. 6 years ago
app.js Merge pull request #1643 from mattgodbolt/features/cdn 3 years ago
package-lock.json Support resolving non-absolute compiler exe values using system path 3 years ago
package.json Support resolving non-absolute compiler exe values using system path 3 years ago
travis-dist-files.txt Support serving static content externally 3 years ago
webpack.config.js Support serving static content externally 3 years ago

README.md

Build Status codecov

Compiler Explorer

Compiler Explorer

Compiler Explorer is an interactive compiler. The left-hand pane shows editable C, C++, Rust, Go, D, Haskell, Swift, Pascal (and some more!) code. The right, the assembly output of having compiled the code with a given compiler and settings. Multiple compilers are supported, and the UI layout is configurable (thanks to GoldenLayout). There is also an ispc compiler ? for a C variant with extensions for SPMD.

Try out at godbolt.org

You can support this project on Patreon.

Compiler Explorer follows a Code of Conduct which aims to foster an open and welcoming environment.

Compiler Explorer was started in 2012 to serve my needs at my previous employer to show how C++ constructs translated to assembly code. It started out as a tmux session with vi running in one pane and watch gcc -S foo.cc -o - running in the other. Since then, it has become a public website serving around 140,000 compilations per day.

FAQ

There is now a FAQ section in the repository wiki. If your question is not present, please contact us as described below so we can help you. If you find that the FAQ is lacking some important point, please free to contribute to it and/or ask us to clarify it.

There are a number of videos that showcase some of the features of Compiler Explorer: A presentation for CppCon 2019 about the project https://www.youtube.com/watch?v=kIoZDUd5DKw and an older 2 part series of videos which go into a bit more detail into the more obscure features https://www.youtube.com/watch?v=4_HL3PH4wDg

Contact us

For general discussion, please join the cpplang slack channel #compiler_explorer or the public mailing list

If you are interested in developing, or want to see the discussions between existing developers, feel free to join the cpplang slack channel #compiler_explorer-development or the development mailing list

Feel free to raise an issue on github or email Matt directly for more help.

Developing

Compiler Explorer is written in Node.js.

Assuming you have a compatible version of node installed, simply running make ought to get you up and running with an Explorer running on port 10240 on your local machine: http://localhost:10240/. Currently Compiler Explorer requires the latest LTS node version (v10) installed, either on the path or at NODE_DIR (an environment variable or make parameter).

Running with make EXTRA_ARGS='--language LANG' will allow you to load LANG exclusively, where LANG is one for the language ids/aliases defined in lib/languages.js. The Makefile will automatically install all the third party libraries needed to run; using npm to install server-side and client side components.

Some languages need extra tools to demangle them, e.g. rust, d, or haskell. Such tools are kept separately in the tools repo.

The config system leaves a lot to be desired. Work has been done on porting CCS to Javascript and then something more rational can be used.

A Road map is available which gives a little insight into the future plans for Compiler Explorer.

Running a local instance

If you want to point it at your own GCC or similar binaries, either edit the etc/config/LANG.defaults.properties or else make a new one with the name LANG.local.properties, substituting LANG as needed. *.local.properties files have the highest priority when loading properties.

When running in a corporate setting the URL shortening service can be replaced by an internal one if the default storage driver isn't appropriate for your environment. To do this, add a new module in lib/shortener-myservice.js and set the urlShortenService variable in configuration. This module should export a single function, see the tinyurl module for an example.

RESTful API

There's a simple restful API that can be used to do compiles to asm and to list compilers.

You can find the API documentation here.

Credits

Compiler Explorer is maintained by the awesome people listed in the AUTHORS file.

We would like to thank the contributors listed in the CONTRIBUTORS file, who have helped shape Compiler Explorer.

We would also like to specially thank these people for their contributions to Compiler Explorer:

We would like to thank JetBrains for their support and for donating licenses to their excellent products to develop Compiler Explorer.

JetBrains