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 314c062c3a Add rust demangling - #213 6 years ago
.idea Add rust demangling - #213 6 years ago
c-preload Allow access to the glibc-compat library 6 years ago
d Fix up D build some more 6 years ago
etc Add rust demangling - #213 6 years ago
examples Merge branch 'master' into msvc-spike 6 years ago
lib Fix intel support in gccs 6 years ago
rust Add rust demangling - #213 6 years ago
static Intel fixes for rust 6 years ago
static-old Tidying up of some old stuff 6 years ago
test Filter out more labels that are unreferenced 6 years ago
.bowerrc First move towards rewrite 6 years ago
.gdb_history 6.1 rc2 7 years ago
.gitignore New most prioritary properties files : `*.local.properties` used for local instances of compiler explorer. 6 years ago
.jshintrc Add IDEA files. 8 years ago
.travis.yml Added support for node 6 6 years ago
LICENSE Update copyright 7 years ago
Makefile Add rust demangling - #213 6 years ago
README.md Revert "Attempt at embedded" 6 years ago
app.build.js Only serve items from out/dist on demand; use @import in CSS instead of lots of includes; configure r.js to optimize CSS too 6 years ago
app.js Support optionally serving versioned data from an extra location 6 years ago
bower.json No longer pin code mirror version in bower 6 years ago
package.json Adding more tests; beginnings of a refactor to make compilers more configurable 6 years ago

README.md

Build Status Codewake

Compiler Explorer

Compiler Explorer is an interactive compiler. The left-hand pane shows editable C/C++/Rust/Go/D 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).

Try out one of the demo sites: C++, Rust, D or Go.

Developing

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/gcc-explorer.defaults.properties or else make a new one with the name gcc-explorer.local.properties. *.local.properties 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.

Credits

Compiler Explorer is maintained by Matt Godbolt. Multiple compiler and difference view was implemented by Gabriel Devillers.