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.
Matt Godbolt dd749f9aba More thanks! 5 years ago
.idea Early support for swift. test with `make EXTRA_ARGS="--language Swift"` 6 years ago
c-preload Allow acces to /proc/cpuinfo 6 years ago
d Adding in LDC opt view support 6 years ago
etc Merge pull request #540 from AndrewPardoe/master 5 years ago
examples Fix max array opt version 6 years ago
haskell Fixed haskell/demangle linker errors on systems without static ghc libs 5 years ago
lib Merge pull request #540 from AndrewPardoe/master 5 years ago
rust Update Rust dependencies 6 years ago
static More thanks! 5 years ago
test Fixes #555 5 years ago
views Finish up Cfg view review concerns 5 years ago
.bowerrc First move towards rewrite 7 years ago
.gdb_history 6.1 rc2 7 years ago
.gitignore Finish up Cfg view review concerns 5 years ago
.jshintrc Add IDEA files. 8 years ago
.travis.yml Hopefully a fix for travis 6 years ago
CODEOWNERS Add @cppchedy to codeowners 5 years ago Update 5 years ago
LICENSE Another year, another copyright update 6 years ago
Makefile Remove all traces of clang-format 5 years ago Update README with API changes 6 years ago Panel->pane in the readme 6 years ago Don't attempt to pack monaco-editor. 6 years ago
app.js Merge pull request #540 from AndrewPardoe/master 5 years ago
bower.json removed logs 5 years ago
package.json Remove all traces of clang-format 5 years ago

Build Status Codewake

Compiler Explorer

Compiler Explorer is an interactive compiler. The left-hand pane shows editable C/C++/Rust/Go/D/Haskell/Swift 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 (the Golden Layout library is used for this). There is also an ispc compiler for a C variant with extensions for SPMD.

Try out one of the demo sites: C++, Rust, D, Go, Haskell, Swif, ispc.

You can support this this project on Patreon.

Developing or running a local instance

Compiler Explorer is written in node.js.

Assuming you have npm and 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/

The Makefile will automatically install all the third party libraries needed to run; using npm to install server-side components and bower to install all the client-facing libraries.

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

The config system leaves a lot to be desired, I'm working on porting CCS to javascript and then something more rational can be used.

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

There's now a Road map that gives a little insight into future plans for Compiler Explorer.


Compiler Explorer is maintained by Matt Godbolt, Rubén Rincón and Simon Brand. Multiple compiler and difference view initially implemented by Gabriel Devillers, while working for Kalray. Clang optview output by Jared Wyles.


There's a simple restful API that can be used to do compiles to asm and to list compilers. In general all handlers live in /api/* endpoints, and will accept JSON or text in POSTs, and will return text responses or JSON responses depending on the request's Accept header.

At a later date there may be some form of rate-limiting: currently requests will be queued and dealt with exactly like interactive requests on the main site. Authentication might be required at some point in the future (for the main Compiler Explorer site anyway).

The following endpoints are defined:

GET /api/compilers - return a list of compilers

Returns a list of compilers. In text form, there's a simple formatting of the ID of the compiler and its description. In JSON, all the information is returned as an array of compilers, with the id key being the primary identifier of each compiler.

POST /api/compiler/<compiler-id>/compile - perform a compilation

To specify a compilation request as a JSON document, post it as the appropriate type and send an object of the form: {'source': 'source to compile', 'options': {userOptions': 'compiler flags', 'compilerOptions':{}, filters': {'filter': true}}}. The filters are an JSON object with true/false. If not supplied, defaults are used. If supplied, the filters are used as-is. The compilerOptions is used to pass extra arguments to the back end, and is probably not useful for most REST users.

A text compilation request has the source as the body of the post, and uses query parameters to pass the options and filters. Filters are supplied as a comma-separated string. Use the query parameter filters=XX to set the filters directly, else addFilters=XX to add a filter to defaults, or removeFilters to remove from defaults. Compiler parameters should be passed as options=-O2 and default to empty.

Filters include binary, labels, intel, comments and directives and correspond to the UI buttons on the HTML version.

The text request is designed for simplicity for command-line clients like curl:

$ curl '' --data-binary 'int foo() { return 1; }'
# Compilation provided by Compiler Explorer at
        push    rbp
        mov     rbp, rsp
        mov     eax, 1
        pop     rbp

If JSON is present in the request's Accept header, the compilation results are of the form:

Optional values are marked with a '**'

  "code": 0 if successful, else compiler return code,
  "stdout": [
              "text": Output,
              ** "tag": {
                          "line": Source line,
                          "text": Parsed error for that line
  "stderr": (format is similar to that of stdout),
  "asm": [
           "text": Assembly text,
           "source": {file: null for user input, else path, line: number} or null if none
  "okToCache": true if output could be locally cached else false,
  ** "optOutput" : {
                     "displayString" : String displayed in output,
                     "Pass" : [ Missed | Passed | Analysis ] (Specifies the type of optimisation output),
                     "Name" : Name of the output (mostly represents the reason for the output),
                     "DebugLoc" : {
                        "File": Name of file,
                        "Line": Line number,
                        "Column": Column number in line
                     "Function": Name of function for which optimisation output is provided,
                     "Args": Array of objects representing the arguments that the optimiser used when trying to optimise