base on Run compilers interactively from your web browser and interact with the assembly [](https://github.com/compiler-explorer/compiler-explorer/actions?query=workflow%3A%22Compiler+Explorer%22) [](https://codecov.io/gh/compiler-explorer/compiler-explorer) [](https://godbolt.org/) # Compiler Explorer Is an interactive compiler exploration website. Edit code in C, C++, C#, F#, Rust, Go, D, Haskell, Swift, Pascal, [ispc](https://ispc.github.io/), Python, Java, or any of the other [30+ supported languages](https://godbolt.org/api/languages) components, and see how that code looks after being compiled in real time. [Bug Report](https://github.com/compiler-explorer/compiler-explorer/issues/new?assignees=&labels=bug&projects=&template=bug_report.yml&title=%5BBUG%5D%3A+) · [Compiler Request](https://github.com/compiler-explorer/compiler-explorer/issues/new?assignees=&labels=request%2Cnew-compilers&projects=&template=compiler_request.yml&title=%5BCOMPILER+REQUEST%5D%3A+) · [Feature Request](https://github.com/compiler-explorer/compiler-explorer/issues/new?assignees=&labels=request&projects=&template=feature_request.yml&title=%5BREQUEST%5D%3A+) · [Language Request](https://github.com/compiler-explorer/compiler-explorer/issues/new?assignees=&labels=request%2Cnew-language&projects=&template=language_request.yml&title=%5BLANGUAGE+REQUEST%5D%3A+) · [Library Request](https://github.com/compiler-explorer/compiler-explorer/issues/new?assignees=&labels=request%2Cnew-libs&projects=&template=library_request.yml&title=%5BLIB+REQUEST%5D%3A+) · [Report Vulnerability](https://github.com/compiler-explorer/compiler-explorer/security/advisories/new) # Overview Multiple compilers are supported for each language, many different tools and visualizations are available, and the UI layout is configurable (thanks to [GoldenLayout](https://www.golden-layout.com/)). Try out at [godbolt.org](https://godbolt.org), or [run your own local instance](#running-a-local-instance). An overview of what the site lets you achieve, why it's useful, and how to use it is [available here](docs/WhatIsCompilerExplorer.md). **Compiler Explorer** follows a [Code of Conduct](CODE_OF_CONDUCT.md) which aims to foster an open and welcoming environment. **Compiler Explorer** was started in 2012 to show how C++ constructs are translated to assembly code. It started as a `tmux` session with `vi` running in one pane and `watch gcc -S foo.cc -o -` running in the other. Since then, it has become a public website serving over [3,000,000 compilations per week](https://stats.compiler-explorer.com). You can financially support [this project on Patreon](https://patreon.com/mattgodbolt), [GitHub](https://github.com/sponsors/mattgodbolt/), [Paypal](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=KQWQZ7GPY2GZ6&item_name=Compiler+Explorer+development&currency_code=USD&source=url), or by buying cool gear on the [Compiler Explorer store](https://shop.spreadshirt.com/compiler-explorer/). ## Using Compiler Explorer ### FAQ There is now a FAQ section [in the repository wiki](https://github.com/compiler-explorer/compiler-explorer/wiki/FAQ). If your question is not present, please contact us as described below, so we can help you. If you find that the FAQ is lacking some important point, please feel free to contribute to it and/or ask us to clarify it. ### Videos Several videos showcase some features of Compiler Explorer: - [Compiler Explorer 2023: What's New?](https://www.youtube.com/watch?v=Ey0H79z_pco): Presentation for CppNorth 2023. - [Presentation for CppCon 2019 about the project](https://www.youtube.com/watch?v=kIoZDUd5DKw) - [Older 2 part series of videos](https://www.youtube.com/watch?v=4_HL3PH4wDg) which go into a bit more detail into the more obscure features. - [Just Enough Assembly for Compiler Explorer](https://youtu.be/QLolzolunJ4): Practical introduction to Assembly with a focus on the usage of Compiler Explorer, from CppCon 2021. - [Playlist: Compiler Explorer](https://www.youtube.com/playlist?list=PL2HVqYf7If8dNYVN6ayjB06FPyhHCcnhG): A collection of videos discussing Compiler Explorer; using it, installing it, what it's for, etc. A [Road map](docs/Roadmap.md) is available which gives a little insight into the future plans for **Compiler Explorer**. ## Developing **Compiler Explorer** is written in [TypeScript](https://www.typescriptlang.org/), on [Node.js](https://nodejs.org/). Assuming you have a compatible version of `node` installed, on Linux simply running `make` ought to get you up and running with an Explorer running on port 10240 on your local machine: [http://localhost:10240/](http://localhost:10240/). If this doesn't work for you, please contact us, as we consider it important you can quickly and easily get running. Currently, **Compiler Explorer** requires [`node` 20](CONTRIBUTING.md#node-version) 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.ts`. For example, to only run **Compiler Explorer** with C++ support, you'd run `make EXTRA_ARGS='--language c++'`. You can supply multiple `--language` arguments to restrict to more than one language. The `Makefile` will automatically install all the third-party libraries needed to run; using `npm` to install server-side and client-side components. For development, we suggest using `make dev` to enable some useful features, such as automatic reloading on file changes and shorter startup times. You can also use `npm run dev` to run if `make dev` doesn't work on your machine. Some languages need extra tools to demangle them, e.g. `rust`, `d`, or `haskell`. Such tools are kept separately in the [tools repo](https://github.com/compiler-explorer/compiler-explorer-tools). Configuring compiler explorer is achieved via configuration files in the `etc/config` directory. Values are `key=value`. Options in a `{type}.local.properties` file (where `{type}` is `c++` or similar) override anything in the `{type}.defaults.properties` file. There is a `.gitignore` file to ignore `*.local.*` files, so these won't be checked into git, and you won't find yourself fighting with updated versions when you `git pull`. For more information see [Adding a Compiler](docs/AddingACompiler.md). Check [CONTRIBUTING.md](./CONTRIBUTING.md) for detailed information about how you can contribute to **Compiler Explorer**, and the [docs](./docs) folder for specific details regarding various things you might want to do, such as how to add new compilers or languages to the site. ### 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`, substituting `LANG` as needed. `*.local.properties` files have the highest priority when loading properties. If you want to support multiple compilers and languages like [godbolt.org](https://godbolt.org), you can use the `bin/ce_install install compilers` command in the [infra](https://github.com/compiler-explorer/infra) project to install all or some of the compilers. Compilers installed in this way can be loaded through the configuration in `etc/config/*.amazon.properties`. If you need to deploy in a completely offline environment, you may need to remove some parts of the configuration that are pulled from `www.godbolt.ms@443`. When running in a corporate setting the URL shortening service can be replaced by an internal one if the default storage driver isn't appropriate for your environment. To do this, add a new module in `lib/shortener/myservice.js` and set the `urlShortenService` variable in configuration. This module should export a single function, see the [tinyurl module](lib/shortener/tinyurl.ts) for an example. ### 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](docs/API.md). ## Contact us We run a [Compiler Explorer Discord](https://discord.gg/B5WacA7), which is a place to discuss using or developing Compiler Explorer. We also have a presence on the [cpplang](https://cppalliance.org/slack/) Slack channel `#compiler_explorer` and we have [a public mailing list](https://groups.google.com/forum/#!forum/compiler-explorer-discussion). There's a development channel on the discord, and also a [development mailing list](https://groups.google.com/forum/#!forum/compiler-explorer-development). Feel free to raise an issue on [github](https://github.com/compiler-explorer/compiler-explorer/issues) or [email Matt directly](mailto:[email protected]) for more help. ## Official domains Following are the official domains for Compiler Explorer: - https://godbolt.org/ - https://godbo.lt/ - https://compiler-explorer.com/ The domains allow arbitrary subdomains, e.g., https://foo.godbolt.org/, which is convenient since each subdomain has an independent local state. Also, language subdomains such as https://rust.compiler-explorer.com/ will load with that language already selected. ## Credits **Compiler Explorer** is maintained by the awesome people listed in the [AUTHORS](AUTHORS.md) file. We would like to thank the contributors listed in the [CONTRIBUTORS](CONTRIBUTORS.md) file, who have helped shape **Compiler Explorer**. We would also like to specially thank these people for their contributions to **Compiler Explorer**: - [Gabriel Devillers](https://github.com/voxelf) (_while working for [Kalray](http://www.kalrayinc.com/)_) - [Johan Engelen](https://github.com/JohanEngelen) - [Joshua Sheard](https://github.com/jsheard) - [Andrew Pardoe](https://github.com/AndrewPardoe) Many [amazing sponsors](https://godbolt.org/#sponsors), both individuals and companies, have helped fund and promote Compiler Explorer. ", Assign "at most 3 tags" to the expected json: {"id":"7195","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"