You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Matt Godbolt 909620cb2c Fixups for add instruction 7 years ago
.idea Do all filtering on the server 7 years ago
c-preload Bump up timeouts and memory limits 7 years ago
d Add clean rule to d/Makefile, and clean up subdirectories in 'make clean' 7 years ago
etc Fixups for add instruction 7 years ago
examples Fix Rust examples for current nightly 7 years ago
lib Fixups for add instruction 7 years ago
static Fix up asm mode to work with msvc 7 years ago
test Fixups for add instruction 7 years ago
.gdb_history 6.1 rc2 7 years ago
.gitignore Add heapsnapshot 8 years ago
.jshintrc Add IDEA files. 8 years ago
.travis.yml Remove stable node from travis for now, as it doesn't like memwatch 7 years ago
LICENSE Update copyright 7 years ago
Makefile Add clean rule to d/Makefile, and clean up subdirectories in 'make clean' 7 years ago
Notes.md Add some notes on LTO version 7 years ago
README.md Clarify the README 7 years ago
app.js More configuration attempts. I wish I had ccs 7 years ago
gdb.txt 6.1 rc2 7 years ago
package.json Hopeful fix for connect-restreamer 7 years ago

README.md

GCC Explorer

GCC Explorer is an interactive compiler. The left-hand pane shows editable C/C++ code. The right, the assembly output of having compiled the code with a given compiler and settings.

Try out the demo site!

Developing

GCC Explorer is written in node.

Assuming you have npm and node installed, simply running make ought to get you up and running with a GCC explorer running on port 10240 on your local machine: http://localhost:10240

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.YOURHOSTNAME.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.