Rivoreo Source Code Repositories
src.rivoreo.one / compiler-explorer / 1986a8069176b8db72cec4c58a2714315d2bde93
commit1986a8069176b8db72cec4c58a2714315d2bde93[log] [download]
authorKārlis Seņko <karlis3p70l1ij@gmail.com>Wed Jan 09 23:04:14 2019 +0200
committerKārlis Seņko <karlis3p70l1ij@gmail.com>Wed Jan 09 23:04:14 2019 +0200
treee4991d3b330204fcced5265b33cb58531de9fd9a
parentf523db681406359a9ad77f7a355a6caa1566e737 [diff]
Enable cfg for x86 LLVM based compilers and gcc.
7 files changed
tree: e4991d3b330204fcced5265b33cb58531de9fd9a
  1. .eslintignore
  2. .eslintrc
  3. .gitattributes
  4. .gitignore
  5. .idea/
  6. .istanbul.yml
  7. .travis.yml
  8. AUTHORS.md
  9. CODEOWNERS
  10. CODE_OF_CONDUCT.md
  11. CONTRIBUTING.md
  12. CONTRIBUTORS.md
  13. LICENSE
  14. Makefile
  15. PULL_REQUEST_TEMPLATE.md
  16. README.md
  17. Roadmap.md
  18. app.build.js
  19. app.js
  20. c-preload/
  21. d/
  22. docs/
  23. etc/
  24. examples/
  25. haskell/
  26. lib/
  27. package.json
  28. rust/
  29. static/
  30. test/
  31. views/
  32. webpack.config.js
  33. yarn.lock
README.md

Build Status codecov

Compiler Explorer

Compiler Explorer

Compiler Explorer is an interactive compiler. The left-hand pane shows editable C, C++, Rust, Go, D, Haskell, Swift and Pascal 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 (thanks to GoldenLayout). There is also an ispc compiler ? for a C variant with extensions for SPMD.

Try out at godbolt.org

You can support this project on Patreon.

Compiler Explorer follows a Code of Conduct which aims to foster an open and welcoming environment.

Contact us

For general discussion, please join the mailing list at https://groups.google.com/forum/#!forum/compiler-explorer-discussion or the cpplang slack channel #compiler_explorer.

If you are interested in developing, or want to see the discussions between existing developers, feel free to join the mailing list at https://groups.google.com/forum/#!forum/compiler-explorer-development or the cpplang slack channel #ce_implementation.

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

Developing

Compiler Explorer is written in Node.js.

Assuming you have a compatible version of 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/. Currently Compiler Explorer requires the latest LTS node version (v8) installed, either on the path or at NODE_DIR (an environment variable or make parameter).

Running with make EXTRA_ARGS='--language LANG' will allow you to load LANG exclusively, where LANG is one for the language ids/aliases defined in lib/languages.js. The Makefile will automatically install all the third party libraries needed to run; using yarn to install server-side and client side components.

The config system leaves a lot to be desired. Work has been done on porting CCS to Javascript and then something more rational can be used.

A Road map is available which gives a little insight into the future plans for Compiler Explorer.

Running a local instance

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

When running in a corporate setting the URL shortening service can be replaced by an internal one to avoid leaking source code outside of the organization. This is done by adding a new module in static/urlshorten-myservice.js and setting the urlShortenService variable in configuration. This module should export a single function, see the google module for an example. urlShortenService can also be set to none to disable url shortening altogether.

RESTful API

There's a simple restful API that can be used to do compiles to asm and to list compilers.

You can find the API documentation here.

Credits

Compiler Explorer is maintained by the awesome people listed in the AUTHORS file.

We would like to thank the contributors listed in the CONTRIBUTORS file, who have helped shape Compiler Explorer.

We would also like to specially thank these people for their contributions to Compiler Explorer:

We would like to thank JetBrains for their support and for donating licenses to their excellent products to develop Compiler Explorer.

JetBrains