f2ec4115f6
Three findings from the GitHub Copilot reviewer, all valid: - Reject non-string releaseTrack overrides early. toProperty in lib/utils.ts coerces "true"/"false"/numeric strings to typed values, so a misconfigured `releaseTrack=true` would have arrived as a boolean and crashed on .trim() with a cryptic TypeError. Type-check the raw value first and emit the same clear assertion message we use for invalid string values. - Backfill releaseTrack on remote-fetched compilers too. fetchRemote() pulls CompilerInfo[] over HTTP from another CE instance; older remotes won't include the field. Without backfill those compilers would land with releaseTrack undefined, breaking the type contract for any consumer that reads it. Apply the same inferReleaseTrack + isReleaseTrack guard used by loadPrediscovered. - Fix the docs/AddingACompiler.md "stable" bullet to match the implemented prerelease-segment rule: a real semver with a `-rc1` / `-preview` suffix classifies as `prerelease`, not `stable`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
How do I ?
This is a how-to guide for the user-interface presented by Compiler Explorer. This doesn't cover the details of how to set up or modify Compiler Explorer for your own needs. For that, please check the documents which already cover topics like:
- Adding a language
- Adding a compiler
- Adding a library
- Adding a tool
- and many more at compiler-explorer/docs
Fast links:
Change the assembly syntax from Intel
The option to switch assembly from Intel to AT&T syntax is present in the Output option of each compiler. If enough
space is not present, the option also presents itself as the gear symbol (⚙)
Compare the time taken by compilation and networking
This is the symbol that looks like a bar graph (📊). If your compilations are taking long, you can use this to check the time taken by:
- Networking, JavaScript, waiting for events, etc.
- Checking the cache and retrieving from it on a cache-hit
- Compilation (on force compilation or cache-miss)
- Parsing the generated assembly before presenting it
View intermediate information provided by the compilers
Though both GCC and Clang create supplementary outputs along with assembly (shown by default), and an executable (created if an executor has been added), the exact nature of the outputs and their formats differ between the compilers.
GCC allows the Tree, IPA, RTL and graph outputs, while Clang allows optimization, AST, IR and graph outputs. Some outputs (e.g. RTL or graph) also have a rich set of options in the UI to enable focussing on a particular function or compiler stage.