Rivoreo Source Code Repositories
src.rivoreo.one / compiler-explorer / 89fab2f121166c191fa193d5234e6416e2f7d0e4
commit89fab2f121166c191fa193d5234e6416e2f7d0e4[log] [download]
authorMatt Godbolt <matt@godbolt.org>Sun Aug 14 09:07:47 2016 -0500
committerMatt Godbolt <matt@godbolt.org>Sun Aug 14 09:21:50 2016 -0500
tree4ab705dd2ca1e213dccd5eb9d170decd58f6f7be
parent7dd1a0ca72c6a887129723b9e3f9a2cd2a1de72f [diff]
More MIPS tweaks
2 files changed
tree: 4ab705dd2ca1e213dccd5eb9d170decd58f6f7be
  1. .gdb_history
  2. .gitignore
  3. .idea/
  4. .jshintrc
  5. .travis.yml
  6. LICENSE
  7. Makefile
  8. Notes.md
  9. README.md
  10. app.js
  11. c-preload/
  12. d/
  13. etc/
  14. examples/
  15. gdb.txt
  16. lib/
  17. package.json
  18. static/
  19. test/
README.md

Build Status Codewake

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.