|b21e51ef27||6 years ago|
|.idea||7 years ago|
|c-preload||6 years ago|
|d||7 years ago|
|etc||6 years ago|
|examples||7 years ago|
|lib||6 years ago|
|static||6 years ago|
|static-old||7 years ago|
|test||6 years ago|
|.bowerrc||7 years ago|
|.gdb_history||7 years ago|
|.gitignore||7 years ago|
|.jshintrc||8 years ago|
|.travis.yml||7 years ago|
|LICENSE||7 years ago|
|Makefile||6 years ago|
|README.md||6 years ago|
|app.build.js||7 years ago|
|app.js||6 years ago|
|bower.json||7 years ago|
|package.json||6 years ago|
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.
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/
Makefile will automatically install all the third party libraries needed to run; using
npm to install server-side
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
*.local.properties files have the highest priority when loading properties.
Feel free to raise an issue on github or email me directly for more help.
Compiler Explorer is maintained by Matt Godbolt. Multiple compiler and difference view was implemented by Gabriel Devillers.